Skip to main content
Glama
beckettlab

Beckett — MCP for Godot

by beckettlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

screenshot

Read-only

Capture an image of the running game or editor viewport to provide the agent with visual context, supporting UI annotation and region-specific inspection.

Instructions

Capture an image the agent can see. target=game (default) captures the RUNNING game; target=editor captures the 2D editor viewport (PNG only). A bare call caps the long edge at max_dim=1280 — pass scale, region, max_dim=0, format or save_to to opt out. annotate=ui draws numbered Set-of-Mark boxes and returns the legend. For pure functional state ui_snapshot is cheaper. Token dials + delivery: help(tool="screenshot").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNo0.05..1.0 downscale before encode (game target; default 1.0)
formatNopng (default) | jpeg | webp (game target)
regionNo[x,y,w,h] pixel crop
targetNogame | editor
deliverNoinline (default) | link (a capture:// resource_link, no base64) | both
max_dimNocap the long edge in px (default 1280 on a call with no other framing argument; 0 = no cap)
qualityNojpeg/webp quality 0.1..1.0 (default 0.8)
save_toNoalso write the frame to this path (res://, user:// or absolute); mints a diff baseline
annotateNo'ui' = draw numbered marks on interactive controls + return the legend (game target)
max_marksNocap on annotate marks (default 40)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.14.0
    • addedInput schema / properties / deliver
      Added value: +{
+  "description": "inline (default) | link (a capture:// resource_link, no base64) | both",
+  "type": "string"
+}
    • addedInput schema / properties / max_dim
      Added value: +{
+  "description": "cap the long edge in px (default 1280 on a call with no other framing argument; 0 = no cap)",
+  "type": "integer"
+}
    • changedInput schema / properties / save_to / description
      Previous value: -"also write the frame to this path (res://, user:// or absolute) so later captures can be diffed against it — the agent still gets the image inline"New value: +"also write the frame to this path (res://, user:// or absolute); mints a diff baseline"
  2. Addedv1.12.1
  3. Removedv1.10.0
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses several non-obvious behaviors beyond the readOnlyHint annotation: the bare-call max_dim cap of 1280, PNG-only restriction for editor captures, annotate behavior with numbered Set-of-Mark boxes and legend return, and the pointer to help for token/delivery controls. This is rich, useful behavioral context.

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 compact and front-loaded, with each sentence earning its place. The closing 'Token dials + delivery: help(tool="screenshot")' is terse and slightly cryptic, which keeps it just short of a perfect structure score.

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

Completeness4/5

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

For a 10-parameter image-capture tool with no output schema, the description covers the core output (image and optional legend), target variants, the dimension cap default, the PNG-only constraint, and a cheaper alternative. It delegates delivery details to help rather than spelling them out, which is a minor completeness gap.

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?

Schema description coverage is 100%, so the baseline is 3; the description adds value by explaining parameter interplay: a bare call applies max_dim=1280, and passing scale, region, max_dim=0, format, or save_to opts out of that default. It doesn't fully document every parameter, but it does meaningful semantic work above the schema.

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

Purpose5/5

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

States a specific action and resource: 'Capture an image the agent can see.' It immediately distinguishes game capture from editor viewport capture, names defaults, and explicitly calls out ui_snapshot as the cheaper functional alternative. This leaves little ambiguity about what the tool is for.

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

Usage Guidelines5/5

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

Provides concrete selection guidance: use target=game for the running game and target=editor for the 2D editor viewport. It also tells the agent when not to use it ('For pure functional state ui_snapshot is cheaper'), which is exactly the kind of alternative routing a tool description should offer.

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