Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_editor_errors

Retrieve Godot editor error logs and stack traces to debug script crashes, runtime exceptions, and compilation failures in game projects.

Instructions

Get editor errors and stack traces. (Compatibility tool)

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": "get_editor_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't explain what triggers the timeout, whether errors are cleared after retrieval, what 'Compatibility tool' implies for behavior, or the return format. The presence of autoConnect suggests connection behavior that isn't explained.

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 extremely concise with no wasted words. However, given the complete lack of schema documentation and annotations, this brevity results in underspecification rather than efficient communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a tool interacting with a live editor process. With no output schema, no annotations, and 0% parameter coverage, the description should explain the parameters, return structure, and the 'compatibility' qualification, but provides none of these.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description adds no information about the parameters. The agent cannot determine what timeoutMs is waiting for (error occurrence? connection?) or what autoConnect connects to, leaving both parameters effectively undocumented.

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 states the tool retrieves 'editor errors and stack traces' with a specific verb and resource. However, the '(Compatibility tool)' parenthetical is opaque and the description doesn't differentiate from sibling diagnostic tools like get_output_log or get_test_report.

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

Usage Guidelines2/5

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

No guidance provided on when to use this tool versus alternatives like get_output_log or get_test_report. The 'Compatibility tool' label hints at legacy usage but doesn't specify when this should be preferred or avoided.

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

Deploy Server

Other Tools