Skip to main content
Glama

find_symbol

Locates indexed code declarations by stable ID, exact or qualified name, or partial name within a repository, returning stable IDs for use with relationship tools.

Instructions

Finds indexed declarations by stable ID, exact name or qualified name, or partial name. Use the returned stable IDs with the relationship tools.

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": {
      "repository_root": "<repository_root>",
      "query": "<query>"
    },
    "name": "find_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesStable symbol ID, declaration name, or qualified name to find.
repository_rootYesAbsolute path to the Git repository root to explore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses that results come from a pre-built index and that partial-name matching is supported, which implies a read-only lookup. It omits result limits, ambiguity/multiple-match behavior, whether matches are ranked, and whether the index can be stale.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the core capability front-loaded and the follow-up usage hint second. Nothing is redundant.

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?

There is no output schema, so the description should say more about what comes back; stating that stable IDs are returned is helpful but leaves the shape of results, match multiplicity, and any result cap unspecified. Adequate for a two-parameter lookup but not complete.

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 both parameters are already documented. The description adds only one detail beyond the schema: that the query may be a partial name, which matters because the schema text lists only stable ID, name, and qualified name.

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 ('Finds indexed declarations') and enumerates the three accepted key forms (stable ID, exact/qualified name, partial name). It does not explicitly distinguish itself from sibling read_symbol, so an agent must infer that this is search-only rather than retrieval-of-contents.

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 second sentence gives a clear downstream workflow hint ('Use the returned stable IDs with the relationship tools'), which tells the agent when this tool fits in a chained call. It gives no guidance on when to prefer this over read_symbol or find_references, and no exclusions.

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