Skip to main content
Glama
Sign In
Sauerbraten MCP

Sauerbraten MCP

by pastukhov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

view_capture

Read-onlyIdempotent

Captures the requested map and view revision as PNG image content for visual inspection of live Sauerbraten level edits.

Instructions

Capture the requested map/view revision as PNG image content.

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": {
      "map_epoch": "<map_epoch>",
      "expected_revision": "<expected_revision>",
      "view_revision": "<view_revision>"
    },
    "name": "view_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
map_epochYes
view_revisionYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is clear. The description adds useful behavioral context by saying the result is PNG image content, but it does not explain revision-mismatch behavior, output size, or how the image is returned.

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 a single front-loaded sentence with no wasted wording. Its brevity is appropriate structurally, though the same brevity contributes to gaps in parameter and behavioral detail.

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?

The tool has three required, undocumented parameters and no output schema, yet the description provides only a high-level one-line summary. It omits the meaning of the two revision parameters and does not clarify how the PNG image content is delivered, leaving meaningful ambiguity for an agent trying 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?

Schema description coverage is 0%, so the description must carry the burden for three required parameters. It mentions 'map/view revision' generally but does not explain what map_epoch is, why expected_revision and view_revision are distinct, or what values are valid beyond the schema's regex patterns.

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 states a specific verb (capture) and resource (requested map/view revision), and names the output format (PNG image content). It is clear what the tool does, though it does not explicitly differentiate itself from any sibling tool by name.

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 explicit guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The phrase 'requested map/view revision' only weakly implies context, leaving the agent to infer that this is for exporting the current map view as an image.

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