Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

find_classes

Read-only

Search Godot classes by name substring across engine, Variant, and project types, optionally filtering to subclasses of a base class; use it as the discovery entry point before describing a class.

Instructions

Search classes by name substring — engine classes, built-in Variant types (Vector3, Transform3D, Color...) AND your project's own types (GDScript class_name + C# [GlobalClass]). Optional 'base' restricts to subclasses (e.g. base=Node2D). The discovery entry point — pair with describe_class.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNomax results (default 50)
baseNoonly subclasses of this class
queryNocase-insensitive name substring

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered. The description adds useful scope context about what universe of classes is searchable, but says nothing about result ordering, truncation behavior at the 'max' limit, or return shape. With annotations carrying safety, a 3 is appropriate.

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 and scope, then the workflow hint. The parenthetical type examples earn their place by clarifying the searchable universe. Slightly dense but no wasted sentences.

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?

For a zero-required-parameter search tool with a rich schema and full read-only annotations, the description covers scope, narrowing semantics, and the follow-up tool. No output schema exists, but an agent has enough to call it correctly without knowing the exact return shape.

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%, so all three parameters are already documented, including the case-insensitive query and the max default of 50. The description reinforces the 'base' semantics with an example but adds little beyond what the schema states. Baseline 3 is correct when the schema does the heavy lifting.

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 (search) and resource (classes) by name substring, and explicitly enumerates scope: engine classes, built-in Variant types, and project GDScript/C# types. It distinguishes itself from the sibling describe_class by positioning itself as the discovery entry point.

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?

Explicitly routes the agent: use this for discovery, then pair with describe_class for detail. The 'base' narrowing is demonstrated with a concrete example (base=Node2D). No explicit when-not-to-use guidance, but the workflow relationship to the sibling is clear.

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