Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_hover

Retrieves type information and documentation for an Ada symbol at a specified file, line, and column so you can inspect declarations without leaving your editor.

Instructions

Get type information and documentation for an Ada symbol

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_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the Ada file
lineYes1-based line number
columnYes1-based column number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure and does not meet it. It never states that this is a read-only, side-effect-free operation, nor what happens when the position does not land on a symbol, nor whether it requires a loaded project.

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 sentence with zero filler and the core purpose front-loaded. It is efficient, though so terse that concision comes at the cost of guidance.

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 simple three-parameter read tool with no output schema, the description covers the essential purpose and the return content at a high level. It falls short on failure behavior and on how the result is shaped (type text, doc string, or both), which an agent would want before calling.

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, and column are already fully documented and the baseline of 3 applies. The description adds no meaning beyond the schema — notably it does not say the coordinates must fall on an identifier to yield results.

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 gives a specific verb and resource: retrieves type information plus documentation for an Ada symbol. It is clear what the tool returns, but it does not distinguish itself from siblings such as ada_type_definition, ada_goto_definition, or ada_get_spec, which an agent could easily confuse with it.

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 statement of when to use this tool versus the many hover-adjacent siblings, and no prerequisites or exclusions are given. The only usage signal is implicit — that a symbol position is needed — leaving the agent to infer the choice.

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