Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

describe_class

Read-only

List a class's properties and methods with signatures so you know exactly which property to set or method to call, including built-in Variant types and custom class_name types.

Instructions

List a class's properties and methods (with signatures) so you know exactly what to set_property / call_method. The discovery key for full domain coverage. Also covers built-in Variant types (Vector3, Transform3D, Basis, Color, String...) and your class_name types.

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

Input Schema

NameRequiredDescriptionDefault
classYes
inheritedNoinclude inherited members (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the read-only hint, the description provides crucial behavioral context, specifying that it covers not only user-defined classes but also critical built-in Variant types like Vector3 and Color, expanding the tool's known scope.

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?

The description is highly efficient, focusing immediately on the core value proposition. Despite its length, every sentence serves a distinct purpose in explaining the tool's utility and scope.

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?

Given that it is a discovery tool, the description is quite complete, detailing exactly what kind of data (properties, methods, signatures, built-in types) the agent will receive, which is more important than detailing the output format itself.

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?

With only 50% schema description coverage, the description provides little extra semantic value for the parameters. While it mentions signatures, it does not elaborate on the functionality of the 'inherited' parameter beyond what the schema implies.

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

Purpose4/5

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

The description clearly defines the tool's function: listing properties and methods with signatures. It is highly effective at differentiating itself by stating its role as the 'discovery key' needed to use sibling tools like set_property and call_method.

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?

It provides strong usage guidelines by explaining the practical implication of its output—providing the necessary details (signatures) to correctly use other tools. It guides the agent on when to invoke it within a workflow.

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