Skip to main content
Glama
Ada MCP Server

Ada MCP Server

ada_workspace_symbols

Search an indexed Ada workspace for symbols by name or pattern using a target Ada file, with optional kind filters and result limits.

Instructions

Search for symbols by name across the complete indexed Ada workspace

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>",
      "query": "<query>"
    },
    "name": "ada_workspace_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to an Ada file which selects the target project/workspace
kindNoFilter by symbol kindall
limitNoMaximum number of results
queryYesSymbol name or pattern to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and delivers very little: "complete indexed workspace" hints at index dependence but never states whether the project must be built/indexed first, how results are ordered, or how matching works despite the schema advertising a "pattern". No mutation, auth, or rate-limit concerns apply, but the search semantics and result behavior remain undisclosed.

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 the action first and the scope second; nothing is redundant. It is efficient, though bordering on under-specified rather than genuinely tight.

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 four-parameter search tool with no output schema and no annotations, the description covers the what and the where but nothing about result shape, ordering, empty-result behavior, or index prerequisites. The schema fully documents parameters, which keeps this adequate, but the behavioral surface is left largely unexplained.

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 all four parameters (file, query, kind, limit) are already documented in the schema, including the enum values and defaults. The description adds only the general notion of name-based searching and contributes no extra detail about pattern syntax, limit effects, or which file to choose.

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 concrete verb and resource ("Search for symbols by name") plus a scope ("across the complete indexed Ada workspace"), which implicitly contrasts with document-scoped lookup siblings like ada_document_symbols. It does not name an alternative explicitly, so differentiation is inferred from the word "workspace" rather than stated.

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?

The phrase "by name" implies this is a name-based discovery tool, as opposed to position-based siblings like ada_goto_definition or ada_find_references, but the description never says when to prefer it or when not to. The requirement to pass a file just to select the project is left entirely to the schema.

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