Skip to main content
Glama
mcintalmo
by mcintalmo

get_godot_class

Read-only

Retrieve a compact map of a Godot class's members and inheritance to quickly understand its API structure and avoid loading full documentation.

Instructions

Return a map of one engine class: what it inherits, what it is for, and the signature of every member it declares, without their descriptions. This is the cheap first call for any question about a class -- some class entries run past 300 KB, so the map is what makes them answerable. Choose the member needed from members, then call get_godot_class_member for its full text. Inherited members are not listed; request a class named in inheritance_chain to see those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoList only members of this kind. Omit for every kind. Worth setting when a full map came back `truncated`.
class_nameYesThe class name, exactly as the engine spells it, e.g. 'Node2D'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesCanonical `godot://class/...` URI.
hintNoWhat to call next to see what was omitted, or to narrow the request. Empty when nothing was left out.
nameYesClass name.
membersNoDeclared members, in source order. Inherited members are not listed; request a class from `inheritance_chain` to see those.
brief_mdNoOne-line summary.
inheritsNoImmediate base class, empty for roots.
truncatedNoWhether content was omitted to stay within the budget.
tutorialsNo`(title, url)` pairs of linked tutorials.
deprecatedNoWhy this class is deprecated; empty if not.
experimentalNoWhy this class is experimental; empty if not.
description_mdNoFull class description, as Markdown.
inheritance_chainNoBase classes from the immediate parent up to the root.
Behavior5/5

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

The description discloses behavior such as returning a map, potential truncation, and omission of inherited members. Combined with readOnlyHint=true annotation, the read-only nature is clear. No contradiction with annotations; description adds valuable context beyond the hints.

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?

The description is concise and well-structured, using three sentences to convey purpose, usage guidance, and edge cases (truncation, inherited members). No redundant wording; each sentence earns its place.

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?

Given the output schema exists, the description adequately explains the return type (map) and how to interact with the results (select a member, follow inheritance_chain). It also covers the truncation scenario. The tool is fully understandable within its context.

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 (class_name and include) with clear descriptions. The tool description does not add additional meaning beyond what is already in the schema, so a baseline score of 3 is appropriate given 100% schema coverage.

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?

The description clearly states the tool returns a map of one engine class, including inheritance, purpose, and member signatures without descriptions. It distinguishes itself as the 'cheap first call' for class questions, differentiating from siblings like get_godot_class_member and search_godot_docs.

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?

The description explicitly advises when to use this tool (first call for any class question) and when to use alternatives (get_godot_class_member for member details, request inherited classes from inheritance_chain). It also explains the truncation behavior and how to follow up with include parameter.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcintalmo/godot-docs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server