Skip to main content
Glama
Sign In
Wick

Wick

by buildepicshit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

gd_lsp_definition

Locates the source file and line number of a symbol in a Godot .gd file by specifying file path, line, and character position.

Instructions

Finds the definition (source file and line) of the symbol at the given 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": {
      "filePath": "<filePath>",
      "line": "<line>",
      "character": "<character>"
    },
    "name": "gd_lsp_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to the .gd file
lineYes0-indexed line number
characterYes0-indexed character/column number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only says 'finds the definition'. It does not disclose what happens if the symbol is not found, performance implications, or whether it requires an active language server.

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?

The description is a single, clear sentence with no unnecessary words. It is front-loaded and efficient.

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?

The tool has no output schema, so the description should explain the return format (e.g., file path and line number). It does not. Also lacks error handling or behavior notes. Sufficient 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% with descriptions for all three parameters. The description adds no additional meaning beyond the schema's definitions, so baseline 3 applies.

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 the tool finds the definition (source file and line) of a symbol at a given position, distinguishing it from siblings like gd_lsp_hover (hover info) and gd_lsp_symbols (list symbols).

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?

No explicit guidance on when to use this tool versus alternatives. The implied usage is when the agent needs to jump to a symbol's definition, but no comparison with gd_lsp_hover or gd_lsp_symbols is provided.

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

Deploy Server

Other Tools