Gear

Overview Schema Source Related Servers Discussions Admin

class-info

Retrieve methods, properties, signals, and enums for a Godot class to find available members before creating nodes, setting properties, or calling runtime methods.

Instructions

[compact alias of query_class_info] Get detailed information about a specific Godot class: methods, properties, signals, enums. Use to discover available properties before calling add_node/create_resource/set_node_properties, or to find methods before call_runtime_method.

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": {
      "projectPath": "<projectPath>",
      "className": "<className>"
    },
    "name": "class-info"
  }
}

Input Schema

Name	Required	Description
`projectPath`	Yes	Absolute path to project directory containing project.godot.
`className`	Yes	Exact Godot class name (e.g., "CharacterBody3D", "StandardMaterial3D", "AnimationPlayer")
`includeInherited`	No	If true, include inherited members from parent classes (default: false — shows only class-specific members)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations provided; description lacks details on side effects, permissions, or output behavior. But it does note it's a compact alias of a query, implying read-only.

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?

Extremely concise: one sentence with an alias note and core purpose. Front-loaded with key information.

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?

No output schema, but description lists return types (methods, properties, etc.). Lacks details on output format or potential errors, which reduces completeness for a query tool.

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 covers all parameters (100% coverage). Description adds no additional parameter semantics beyond the schema.

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?

Explicitly states the tool provides detailed class info (methods, properties, signals, enums) and gives concrete use cases for discovering properties before other actions. Distinguishes from sibling tools like class-query.

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?

Directly advises when to use: before calling add_node, create_resource, set_node_properties, or call_runtime_method. Provides clear context for invocation.

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