Skip to main content
Glama

get_capabilities

Return a filtered catalog of tools from the godot-devtool server, with options to include schemas and filter by route group, transport, risk level, or search query.

Instructions

Return a lightweight godot-devtool tool catalog by default, with optional filtered input schemas by route group, transport, risk level, tool name, or query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeSchemasNoInclude input schemas for the filtered tools. Defaults to false and requires routeGroup, transport, riskLevel, toolNames, or query when true.
routeGroupNoOptional route group filter such as project, scene, node, visual, editor, runtime, filesystem, resource, script, or core.
transportNoOptional transport filter such as native, headless_godot, process_control, editor_ws, or runtime_ws.
riskLevelNoOptional risk-level filter such as read, write, destructive, or process.
toolNamesNoOptional exact tool names to return. When provided, results follow this requested order.
queryNoOptional case-insensitive search across tool name, description, route group, transport, risk level, and canonical name.
workflowNoOptional focused workflow filter for compact context. Use this instead of requesting all schemas.
compactNoReturn compact JSON. Defaults to true; set false for pretty-printed JSON.
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It mentions the default lightweight output and optional filtering, but does not state that the tool is read-only, has no side effects, or describe the output format beyond 'catalog'. The behavioral implications of the 'workflow' parameter (returning a predefined set) are not explained.

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 a single sentence of about 25 words, front-loading the core purpose. Every word contributes meaning, with no redundancy or unnecessary detail.

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?

Given 8 parameters, no annotations, and no output schema, the description is brief. It does not describe the structure of the returned catalog (e.g., array of tool objects with fields), nor does it clarify that the tool is a safe introspection operation. While adequate for a simple tool, it lacks detail needed by an agent to fully understand the output and side effects.

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?

The input schema has 100% description coverage, so the schema already defines parameters clearly. The description adds value by summarizing filter types and providing extra guidance for the 'workflow' parameter ('Use this instead of requesting all schemas'). However, it does not detail other parameter specifics beyond what the schema provides.

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 'lightweight godot-devtool tool catalog' with filtering options by route group, transport, risk level, tool name, or query. This distinguishes it from sibling tools like 'get_godot_version' (version info) and 'list_projects' (project listing).

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

Usage Guidelines3/5

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

The description implies the tool is for exploring available tools/capabilities but does not explicitly state when to use this tool versus alternatives. For example, it does not say 'Use this to discover available tools; use get_godot_version for version info.' The guidance is implicit but not explicit.

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/wangdiandao/godot-devtool'

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