Tools

5 tools in 2 families. The names, descriptions and schemas are generated from the server itself, so they are exactly what the model receives in tools/list.

Indexes a C# codebase with Roslyn and answers an agent with that codebase's own idioms, so generated code reads like the code around it rather than like generic C#. index_codebase builds the index; every other tool answers from it and never opens a workspace. An empty answer explains itself: "nothing is indexed" and "nothing matched" are different facts.

Tool Family What it does
index_codebase Building the index Builds or refreshes the index of a C# codebase with Roslyn.
search_code_patterns Answers from the index Finds how this codebase does a thing, by meaning rather than by name.
get_di_conventions Answers from the index Shows how this codebase registers a service: the registrations of the named contract, the module methods that own them, and the lifetimes used across the cod…
get_guidelines Answers from the index The rules this codebase is written by: how it is layered, how a type is shaped, how failure is reported, how members are named and documented.
get_dto_format Answers from the index The written contract style of this codebase, with real declarations from it that follow the style.

Resources

Name What it does
codebase://architecture-guidelines The architecture conventions this codebase keeps in writing: what a result type is, how failure is reported, what a contract looks like. Read this before designing anything for it.