Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_document_symbols

Extract all symbols defined in an Ada file to generate a structured outline of declarations for navigation and code analysis.

Instructions

Get all symbols defined in an Ada file (outline)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "ada_document_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden; 'Get' implies a read-only lookup, which is correct but only implicit. It says nothing about whether the outline is hierarchical, whether nested/local symbols are included, or how non-Ada or unparsable files are handled. For a low-risk read query this is tolerable but thin.

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?

A single short, front-loaded sentence with no filler, verb first and resource second. It is arguably too terse for the amount of behavioral information omitted, but nothing in the text is wasted.

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?

For a one-parameter, read-only query tool with no output schema, the definition covers the essential inputs and the scope of results. However, since no output schema exists, the description should say more about what an 'outline' contains, which is exactly the ambiguity an agent would hit when deciding between this and workspace symbols.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains 'file' as an absolute path to an Ada file. The description reinforces that the file must be an Ada file but adds no format or path-handling detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource — 'Get all symbols defined in an Ada file' — with the scope clearly bounded to a single file and the parenthetical '(outline)' hinting at the result shape. It does not name the sibling ada_workspace_symbols, so the file-vs-workspace distinction must be inferred from the word 'file'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no alternative is named even though ada_workspace_symbols is an obvious near-neighbor. The phrase '(outline)' implies a per-file outline view, but the agent must guess that this is the right choice for single-file navigation rather than workspace-wide search.

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