Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

find_methods

Read-only

Search Godot methods by name substring and optionally limit results to a class, including inherited and built-in Variant methods, so you can find the correct callable or built-in operation.

Instructions

Search methods by name substring, optionally restricted to a class (incl. inherited). Covers engine classes, built-in Variant types (Vector3, Transform3D, Color...) and your class_name types. Object methods are invokable via call_method; kind=builtin results are called on values in GDScript. An unknown class is an error, never a silent search of everything.

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

Input Schema

NameRequiredDescriptionDefault
maxNo
classNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.1
  2. Removedv1.10.1
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/not-destructive/not-openWorld, so the safety profile is covered. The description adds genuinely useful behavior beyond that: inherited methods are included, an unknown class is a hard error (not a silent full search), and results carry a 'kind' distinction relevant to how they're called. Return format/pagination via 'max' remains undisclosed.

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 tight sentences, purpose front-loaded, followed by coverage scope and behavioral caveats. Every sentence earns its place with no redundancy.

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

Completeness4/5

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

No output schema exists, so return shape is the description's responsibility; it hints at a 'kind' field and the builtin-vs-object call distinction but never states the result structure. For a read-only search with annotations covering safety, the rest (coverage, error semantics, downstream calls) is adequately 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 0%, so the description must carry parameter meaning. It does well for two of three: 'query' is a name substring and 'class' is an optional restriction including inherited methods. The 'max' parameter is never explained, leaving one third of the parameters undocumented in both schema and description.

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?

States a specific verb+resource ('Search methods') with precise scoping: 'by name substring, optionally restricted to a class (incl. inherited)'. The coverage sentence (engine classes, built-in Variant types, user class_name types) distinguishes it from find_classes and describe_class without opening either schema.

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

Usage Guidelines4/5

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

Routes the agent onward: 'Object methods are invokable via call_method; kind=builtin results are called on values in GDScript' tells it what to do after finding a method. It also clarifies error behavior for unknown classes. No explicit when-not or sibling-by-name exclusion, but the context is clear.

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