Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

clear_editor_errors

Clears the Godot editor output panel's error list so you can reset error feedback before new diagnostics or debugging sessions.

Instructions

Clear the error list in the Godot editor output panel.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for what is effectively a state-mutating/cleanup operation. It does not say whether cleared errors are permanently lost, whether the call fails when no editor is running, or whether clearing affects the output panel beyond errors, which matters when choosing this over a read-only sibling.

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?

A single front-loaded sentence with no redundant wording; every clause (verb, resource, location) adds meaning. It is appropriately sized for a trivial operation, though there is no additional structure because there is nothing more stated.

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?

For a zero-parameter, no-output tool the description is close to sufficient, but with no annotations it should at least signal that this discards error state and how it relates to get_editor_errors. As written it is adequate but leaves a real gap around consequences of the call.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain; baseline is 4. Nothing in the description contradicts the empty schema.

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?

States a specific verb and resource (clear the error list) and scopes it to the Godot editor output panel, so the action is unambiguous. It does not name the obvious counterpart get_editor_errors or otherwise differentiate itself from siblings, so the agent must infer the read-vs-clear distinction from names alone.

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?

There is no when-to-use or when-not-to-use guidance: nothing says to call this after resolving errors, or that get_editor_errors should be used to read errors first. Usage is only implied by the verb 'clear', leaving the agent to guess at the workflow.

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