Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_signature_help

Retrieves function or procedure signature help at a specific file, line, and column to show parameter details while coding Ada.

Instructions

Get function/procedure signature help at a position

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

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about what is returned, what happens at a position outside a call expression, or whether the file must be part of an open project. For a position-sensitive lookup tool this leaves notable gaps.

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 no filler or redundancy. It is efficient, though its brevity contributes to the missing behavioral detail rather than reflecting disciplined prioritization.

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

Completeness2/5

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

With no annotations, no output schema, and three required positional parameters, the description should clarify the return shape (e.g. parameter list with the active parameter) and any failure mode. It provides none of that, leaving the agent to guess the response semantics.

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%, so file/line/column are already fully documented as an absolute path and 1-based coordinates. The phrase 'at a position' adds only marginal framing on top of that, so the baseline 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?

The description names a specific verb ('Get') and a specific resource ('function/procedure signature help') qualified by position, which is meaningfully distinct from sibling tools like ada_hover or ada_completions. It stops short of explicitly contrasting itself with those siblings, so an agent must infer the boundary.

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 guidance on when to reach for this versus alternatives such as ada_hover, ada_completions, or ada_get_spec, and no mention of preconditions (e.g. cursor must be inside an argument list). Usage is only implied by the term 'signature help'.

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