Skip to main content
Glama

Find usages

godot_usages
Read-onlyIdempotent

Find every use of a function, signal, variable, class, node, group, input action or res:// path across a Godot project before renaming, moving or deleting it.

Instructions

Find every place a name is used in the project, offline: a function, signal, variable, constant, class_name, autoload, input action, group or node name, or a res:// path / uid:// (which files refer to it, and whether it exists). Looks in GDScript (not comments), in strings where Godot looks names up (connect, emit_signal, is_action_pressed, add_to_group, get_node, load), in scene connections, node names and groups, and in project settings. Returns the definition, then each use with file, line, kind and the line itself (very common names are capped). Call it before you rename, move or delete anything; godot_rename makes the change everywhere. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
nameYeswhat to look for, e.g. take_damage, health_changed, Player, jump, res://scenes/enemy.tscn
pathNoproject folder, or a file or folder inside it (relative to the server's folder; default: the current project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / path / description
      Previous value: -"The project folder, or any file or folder inside it (Godotwright walks up to project.godot). Relative paths start at the server's folder. Default: the current project."New value: +"project folder, or a file or folder inside it (relative to the server's folder; default: the current project)"
  2. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / path / description
      Previous value: -"Project directory or a path inside it (default: the current project)."New value: +"The project folder, or any file or folder inside it (Godotwright walks up to project.godot). Relative paths start at the server's folder. Default: the current project."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world) and the description never contradicts them, adding the read-only claim explicitly. Beyond that it discloses the search surface (GDScript excluding comments, name-lookup strings such as connect/emit_signal/get_node/load, scene connections, node names, groups, project settings) and a result-shaping behavior agents must know: very common names are capped.

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?

Front-loaded with the core action, then search scope, return shape, and call timing in a logical order with zero filler. The single dense paragraph with long parenthetical lists is efficient but harder to scan than it could be; no sentence is removable, though.

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?

There is no output schema, so the description carries the return contract itself and does: definition first, then each use with file, line, kind and the source line, plus the truncation caveat. For a two-parameter read tool this is complete enough to call and interpret correctly.

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%, so the baseline is 3; the description earns a bump by clarifying that `name` accepts uid:// references (absent from the schema examples) and that a path argument also reports "whether it exists", not just where it is referenced. It does not restate the `path` default semantics, which the schema already handles.

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?

"Find every place a name is used in the project, offline" gives a specific verb plus scope, then enumerates exactly what counts as a name (function, signal, variable, class_name, autoload, input action, group, node name, res:// path / uid://). An agent can distinguish this from godot_rename or godot_deps without opening the schema.

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?

States the trigger explicitly: "Call it before you rename, move or delete anything", and names the alternative that performs the mutation ("godot_rename makes the change everywhere"). No inference is required about when this tool versus its sibling applies.

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