Skip to main content
Glama

godot_review_capture

Capture a prepared Godot review as a source-bound image in an isolated browser, saving it to a specified directory.

Instructions

Capture the prepared review in an isolated browser.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "directory": "<directory>"
    },
    "name": "godot_review_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already state readOnly=false, idempotent=false, destructive=false, and openWorld=false, so the safety profile is covered. The description adds only that the browser is "isolated," but does not say whether a headless browser is launched, whether it persists, what timeout or resource expectations apply, or that this is a non-idempotent side-effecting operation.

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

Conciseness3/5

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

One sentence with no filler and the mechanism front-loaded, but it is undersized rather than well-calibrated: there is no wasted wording because there is barely any wording, leaving the key terms undefined.

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?

An output schema exists so return values need not be explained, but for a non-read-only, non-idempotent tool with an undocumented required parameter, the description omits the input's meaning, the prerequisite workflow, and any environment or side-effect expectations an agent needs to call it correctly.

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

Parameters2/5

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

The single required parameter "directory" has 0% schema description coverage, so the description carries the full burden and supplies nothing — it never says whether this is the review directory path, an output location, or a relative vs absolute path, nor any format constraints.

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

Purpose3/5

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

"Capture the prepared review in an isolated browser" gives a verb (capture) and a resource (the prepared review) plus a mechanism (isolated browser), but "capture" is ambiguous — screenshot, render, record, or serialize — and the description never distinguishes this from siblings like godot_review_prepare or godot_review_inspect.

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?

The word "prepared" weakly implies a prior godot_review_prepare step, which is the only usage signal. There is no explicit when-to-use, no when-not-to-use, no mention of what to do after capture, and no reference to the sibling tools that bookend this step.

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