Skip to main content
Glama

godot_review_inspect

Read-onlyIdempotent

Checks review hashes for a directory, reports pending cleanup, and returns the latest attempt to verify review state.

Instructions

Check review hashes and report pending cleanup and the latest attempt.

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_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the tool checks hashes and reports pending cleanup and the latest attempt, but it does not elaborate on operational behavior such as auth needs or pagination.

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 definition is a single front-loaded sentence with no filler. It is appropriately brief, though the phrase "latest attempt" is somewhat ambiguous without additional context.

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?

The output schema exists, so return values need not be explained, and annotations cover safety behavior. However, the description leaves the sole parameter undocumented and provides no usage context relative to sibling tools, which are notable gaps for a one-parameter inspection tool.

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?

There is one required parameter, directory, and schema description coverage is 0%. The description never mentions what directory means, what path format is expected, or what directory scope should be supplied, so it fails to compensate for the missing schema documentation.

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 uses a specific verb-resource pair: "Check review hashes" and "report pending cleanup and the latest attempt." This makes the inspection purpose clear, though it does not explicitly differentiate itself from siblings like godot_review_capture or godot_review_prepare.

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 description states what the tool does but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not say when an agent should choose this inspection tool over godot_status or the other review tools.

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