Skip to main content
Glama

krusch_git_file_symbols

Read-onlyIdempotent

List AST symbols and line spans in a specified file to map structure before editing. Use it to locate definitions and reference exact code ranges.

Instructions

List all extracted AST symbols and line spans within a specific file.

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_path": "<file_path>"
    },
    "name": "krusch_git_file_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds that the output contains AST symbols plus line spans, a useful hint about payload shape, but says nothing about cost, limits, or behavior on a file with no parseable symbols.

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 efficient sentence with the resource front-loaded and no filler. It is arguably too terse given the undocumented repo parameter, but as structure goes there is no wasted wording.

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 2-parameter read tool with annotations and no output schema, the description covers the core behavior adequately. It is incomplete on the repo parameter and on whether output is paginated or truncated, which matters for large files.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 2 parameters, so the description carries the full burden and only partly delivers: 'within a specific file' pins down file_path, but the 'repo' parameter is never mentioned and its relationship to file_path is unexplained. With zero schema coverage this leaves an agent guessing on half the inputs.

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 ('List') and resource ('extracted AST symbols and line spans') with a clear scope ('within a specific file'), so the agent knows exactly what comes back. It stops short of distinguishing itself from the sibling krusch_git_search_symbols, which an agent could easily confuse it with.

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 by the phrase 'within a specific file' — the agent can infer this is the per-file lookup rather than a repo-wide search. There is no explicit when-to-use/when-not guidance and no named alternative despite search_symbols being an obvious sibling.

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