aicb-roslyn-mcp

Overview Schema Source Related Servers Discussions Admin

Get Server Info

server_info

Read-onlyIdempotent

Report the server's identity and health—name, version, build commit, config DB schema version, and drift warnings—to verify the running binary matches your code after connect, update, or restart.

Instructions

Report this SERVER's own identity and health: name, version, build commit, the config DB's schema version, and drift warnings about the server binary. Needs no session - a reachability smoke-check.

Call it first after connecting and after an update or restart: the commit answers the question the version number cannot - 'is the binary I am talking to built from the code I just landed?'. It says nothing about a solution's configuration (solution_config_status: what is active; check_solution_config_drift: does it still fit the code), about which tools exist (list_skills) or about how they were used (usage_report).

Returns plain text, not JSON. Line 1 is the identity: 'aicb MCP server (AIContextBuilder) v (commit )'. Compare the commit against git rev-parse HEAD (the full sha, so a short hash is its prefix): one version number can cover DIFFERENT builds. A build with no resolvable git revision omits the commit. 'Config DB schema: user_version=N ()' follows when a config DB is resolved.

Then, only when they apply: ANALYZER DRIFT - this build's commit against the HEAD of each repo of a solution this server analyzed, per repo with its solution and HEAD (it cannot tell which is yours); also in-sync and ahead; silent with no session; a repo not knowing this commit gets no line. SCHEMA DRIFT - the config DB's schema is newer than this binary: rebuild or reinstall. PENDING MIGRATION - the reverse: the DB is older; the line says how to migrate it. TOOL POOL DRIFT - the active profile lists tools this binary does not register: a newer build wrote it (rebuild or reinstall) or the tool was retired (re-save the profile). That check is tool-NAME level; a new parameter on an existing tool is not detected, the commit is the finer signal. CONFIG DRIFT - the active MCP profile changed since this server started: restart or reconnect to load the current tools and instructions.

Read-only: it reads the config DB's schema version and, for the analyzer line, queries git in the analyzed solution's repository.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "server_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial beyond-schema context: no session required, plain-text rather than JSON return, that it reads the config DB schema version and shells out to git in the analyzed repo, and that analyzer drift is silent without a session. It also discloses a real limitation ('a new parameter on an existing tool is not detected') so the agent knows the boundary of the check.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with identity and the recommended call point before any drift detail, and each drift paragraph pairs a symptom with an action (rebuild, re-save, restart, migrate). The drift block is dense and heavy on parentheticals, running longer than a no-parameter tool strictly requires, but almost every clause carries distinct diagnostic value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the full burden of explaining the return value and does so precisely: line 1 format, the literal 'Config DB schema: user_version=N' line, the omitted-commit case, and each conditional drift section tied to a remedy. Everything an agent needs to call and interpret the result is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters with an empty object schema, so there is nothing for the description to disambiguate; the baseline applies. The space it would spend on parameters is instead spent on interpreting the return payload, which is the more useful investment here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific resource and scope ('this SERVER's own identity and health') and enumerates the exact fields returned: name, version, build commit, config DB schema version, drift warnings. It then explicitly distinguishes itself from three siblings (solution_config_status, check_solution_config_drift, list_skills, usage_report), so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Call it first after connecting and after an update or restart') plus the reasoning behind the commit check. It also names the tools to use instead for adjacent questions and states the conditions under which drift sections do or do not appear ('silent with no session'), leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server