Skip to main content
Glama

gdscript_references_batch

Read-only

Batch find references for multiple GDScript symbols in one call. Use zero-based coordinates for bulk impact analysis across files.

Instructions

Find references for multiple symbols in a single call. Returns: list of reference locations for each position. IMPORTANT: Uses ZERO-BASED coordinates. More efficient than calling gdscript_references repeatedly. Use for bulk impact analysis across multiple symbols.

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": {
      "positions": "<positions>"
    },
    "name": "gdscript_references_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionsYesList of positions to find references for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.6
    • changedInput schema / properties / positions / description
      Previous value: -"List of positions"New value: +"List of positions to find references for"
    • addedInput schema / properties / positions / items / properties / character / description
      Added value: +"Zero-based character position"
    • addedInput schema / properties / positions / items / properties / file / description
      Added value: +"Path to .gd file"
    • addedInput schema / properties / positions / items / properties / line / description
      Added value: +"Zero-based line number"
  2. First observedv1.0.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true (safe read). Description adds that it returns a list of reference locations and emphasizes zero-based coordinates, which is valuable behavioral context beyond the schema. No contradictions.

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?

Three sentences with no waste: purpose, return info + key constraint, usage guidance. Front-loaded with critical details.

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

Completeness5/5

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

Given one parameter, no output schema, and annotations covering read-only/open-world, the description fully covers the tool's purpose, return value, usage context, and key behavioral note (zero-based).

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

Parameters4/5

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

Schema coverage is 100% with detailed property descriptions. The description reinforces the zero-based coordinate requirement with an IMPORTANT note, adding value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Find references for multiple symbols in a single call' with a specific verb and resource, and distinguishes from the sibling `gdscript_references` via the 'batch' aspect and efficiency mention.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'More efficient than calling gdscript_references repeatedly' and 'Use for bulk impact analysis across multiple symbols', providing clear when-to-use and why it is better than the alternative.

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