Forge Engine MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it captures a screenshot (implying a read-only operation) and returns a base64-encoded PNG image. However, it lacks details on potential side effects (e.g., performance impact, viewport changes), error conditions, or limitations (e.g., resolution, timing). The description adds basic context but is not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose ('Capture a screenshot...') followed by additional context on return format and usage. Every sentence adds value: the first defines the action, the second explains output and high-level use case. It is efficient with zero waste.

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

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

Given the tool's moderate complexity (capturing visual data) and lack of annotations or output schema, the description is minimally adequate. It covers what the tool does and the return format, but does not address potential behavioral nuances (e.g., what 'current viewport' entails, failure modes). For a tool with no structured output documentation, more detail on the returned image or usage constraints would improve completeness.

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

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's function. Baseline is 4 for zero parameters, as it avoids unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Capture a screenshot of the current Godot viewport.' It specifies the verb ('capture') and resource ('screenshot'), but does not explicitly differentiate it from sibling tools like 'forge_get_scene_tree' or 'forge_get_properties' that also retrieve visual/state information. The purpose is specific but lacks sibling comparison.

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

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

The description provides implied usage guidance with 'Use this to "see" the game or editor state,' suggesting it's for visual inspection. However, it does not explicitly state when to use this tool versus alternatives (e.g., 'forge_get_scene_tree' for structural data or 'forge_get_properties' for property values), nor does it mention any prerequisites or exclusions. The guidance is contextual but incomplete.

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