Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_find_references

Finds all references to an Ada symbol across the project from a file, line, and column position, so you can trace where it is used and optionally include its declaration.

Instructions

Find all references to an Ada symbol across the project

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>",
      "line": "<line>",
      "column": "<column>"
    },
    "name": "ada_find_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
lineYes1-based line number
columnYes1-based column number
include_declarationNoInclude the declaration in results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Find' and 'across the project' imply a non-mutating, project-scoped query, but nothing is said about result shape (locations vs. symbols), whether results are grouped by file, or any cost/latency characteristics of a project-wide scan.

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 front-loaded sentence with zero filler, and the scope qualifier is placed where it matters. It is efficient but arguably under-specified rather than optimally concise.

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?

The tool has four parameters with full schema coverage and no annotations, and it lacks an output schema, so the description is the only place the return value could be characterized. It never says what a reference result looks like, leaving a real gap for an agent that must interpret the response.

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 description coverage is 100%, so file, line, column, and include_declaration are already fully documented in the schema. The description adds no extra meaning such as whether the position must be on the identifier itself, so the baseline of 3 applies.

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 ('Find all references to an Ada symbol') plus scope ('across the project'), which is clearly distinct from definition/hover-style lookups. It does not name a sibling such as ada_goto_definition or ada_implementation to sharpen the boundary, so it stops short of 5.

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

Usage Guidelines3/5

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

Usage is only implied: 'find all references' suggests a project-wide symbol usage search rather than a single-definition lookup, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the distinction from the verb alone.

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