Skip to main content
Glama
gregordadera

aicb-roslyn-mcp

by gregordadera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Check Solution Configuration Drift

check_solution_config_drift
Read-onlyIdempotent

Checks if a solution's layer profile, exclusion list, and test profile still fit the code, flagging stale namespaces or test projects so you know which config to rebuild.

Instructions

Check whether a solution's active Layer Profile, Exclude-Namespaces and Test Profile still FIT the code. solution_config_status tells you WHICH configuration is active and where it comes from.

Use it on a solution configured a while ago, or when layer or exclusion results look off; a stale axis is rebuilt with init_solution_config and apply_solution_config. Do not use it on a never-configured solution: nothing is evaluated there.

Three conservative signals: layer - declared (own) namespaces that no rule of the active layer profile maps; exclusion - EXTERNAL referenced namespaces that the active exclusion list does not cover; test - projects the default heuristic classifies as test projects that the active custom test profile's rules do not match.

Returns JSON with layer, exclusion and test, each carrying source (db / sidecar / built-in / none), name, status, stale, considered (the denominator), sample (the drifted names as items/count/totalFound/truncated, max 50) and reason, which states the drifted count against considered. status is 'stale' from 3 drifted names on for layer and exclusion, and for test when more than a quarter of the considered projects drifted; else 'ok', and an 'ok' with a sample is still worth reading. 'built-in-preset' and 'not-configured' mean the axis was NOT evaluated: only a custom config is judged (a generic preset is a choice, not drift). sidecarProblem appears when the .aicb.json could not be read.

It changes no configuration and creates no solution row; a dbPath that does not exist is refused with an error, and an older one is upgraded on open (schema, built-in rows), as the server's own DB is at startup. It judges the configuration a plain analyze_solution resolves NOW, not a layerProfile the session was analyzed with. It needs a live session, not a recalled one.

Parameters: normally pass only sessionId (an absolute .sln path works too). Pass dbPath only if the session was analyzed with that same dbPath; otherwise this judges a configuration the analysis did not use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbPathNoOptional absolute path to the aicb config/master DB. If given, the config the DB holds for the solution (per-solution row, then app-global default) takes precedence over the .aicb.json sidecar; a built-in default in the DB does not. Omit to fall back to the server's default config DB (the GUI's, if resolved), else only the .aicb.json sidecar next to the .sln.
sessionIdYesThe session_id returned by analyze_solution. Also takes an absolute .sln/.slnx/.slnf path, analyzed on first use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.46513
    • changedInput schema / properties / sessionId / description
      Previous value: -"The session_id returned by analyze_solution."New value: +"The session_id returned by analyze_solution. Also takes an absolute .sln/.slnx/.slnf path, analyzed on first use."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive; the description adds genuinely new behavior: it changes no configuration, creates no solution row, refuses a nonexistent dbPath with an error, upgrades an older DB on open, judges the config a plain analyze_solution resolves now, and requires a live (not recalled) session. The only gap is no note on performance or rate characteristics, but the behavioral surface is well covered.

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 the core question and the sibling contrast before the details; every sentence carries information. It is dense and long, but the length is justified by the absence of an output schema and the non-obvious dbPath precedence rules.

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 fully specifies the return shape (layer/exclusion/test axes, source/name/status/stale/considered/sample/reason fields, status thresholds, built-in-preset and not-configured semantics, sidecarProblem). An agent has everything needed to call and interpret it.

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?

Schema coverage is 100% (baseline 3), but the description adds decision guidance beyond the schema: 'normally pass only sessionId' and pass dbPath only if the session was analyzed with that same dbPath, otherwise the judgment is meaningless. That is real added meaning, not a restatement.

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?

States a specific verb+resource ('Check whether a solution's active Layer Profile, Exclude-Namespaces and Test Profile still FIT the code') and explicitly differentiates from the sibling solution_config_status by contrasting 'which config is active' vs 'does it still fit'.

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 explicit triggers ('a solution configured a while ago, or when layer or exclusion results look off'), an explicit exclusion ('Do not use it on a never-configured solution: nothing is evaluated there'), and names the remedial siblings init_solution_config and apply_solution_config.

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

Deploy Server

Other Tools