Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_diagnostics

Retrieve synchronized Ada compiler diagnostics for a specific file, or inspect the incomplete cache of published diagnostics when no file is given. Filter results by severity.

Instructions

Get synchronized compiler diagnostics for one Ada file, or the explicitly incomplete cache of published diagnostics when no file is provided

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": "ada_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoAbsolute path to Ada file, or omit for all files
severityNoFilter by severity levelall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one high-value trait — the no-file mode returns an 'explicitly incomplete' cache rather than full data — and implies freshness with 'synchronized'. However, it says nothing about whether the call triggers a compile/build, how costly or slow it is, or what a diagnostic record looks like.

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

Conciseness5/5

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

A single well-formed sentence with the primary case (one file) front-loaded and the fallback case trailing. Every clause carries information; nothing is repeated from the title or schema.

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

Completeness3/5

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

With no output schema and no annotations, the description must cover both behavior and returns, and it covers only the former. An agent still cannot tell what a returned diagnostic contains (line/column, severity, message), whether results are cached per file, or what triggers recompilation. Adequate to select the tool, thin for invoking it confidently.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are documented in the schema, so the baseline is 3. The description adds one real nuance — that omitting 'file' yields the incomplete published cache rather than a complete workspace scan — but adds nothing about 'severity' (e.g. whether 'all' subsumes hints) beyond the existing enum and default.

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

Purpose4/5

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

The description states a specific verb and resource ('Get ... compiler diagnostics') and scopes it to 'one Ada file', which separates it from the other ada_* navigation/lookup tools. It stops short of naming a sibling (e.g. ada_build, which could also surface build output), so an agent must infer the boundary rather than being told it.

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

Usage Guidelines4/5

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

Clear conditional guidance: supply a file for synchronized results, omit it to get the published-diagnostics cache. The phrase 'explicitly incomplete cache' steers the agent toward passing a file when accuracy matters, which is genuine when-to-use advice. It lacks explicit when-not-to-use or a named alternative.

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