Skip to main content
Glama

game_screenshot

Read-only

Capture a FiveM game screenshot via window or bridge and compare it to a named visual baseline to detect UI regressions, returning a diff percentage and diff image.

Instructions

Screenshot the game. auto/window captures the local FiveM window including NUI; game uses the bridge (no NUI, works for remote clients). baseline names a visual baseline: saved on first use (or with saveBaseline), compared afterwards (returns diffPercent and a diff image when over 0.5%).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoauto
playerNo
serverNo
baselineNo
maxWidthNo
saveBaselineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so safety is covered; the description adds genuinely useful behavior such as NUI inclusion, remote-client support, and the baseline compare return values. However, it does not disclose the notable side effect that the first baseline call writes a baseline file, nor what the saved image looks like or where it goes — context that matters for a tool flagged read-only.

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?

Two dense sentences, capture modes front-loaded before the baseline behavior, with no filler. The nested parentheticals make it slightly harder to scan but every clause carries real information.

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?

No output schema exists, and the description does cover the baseline return contract (diffPercent plus a diff image over 0.5%), which is the most important return detail. It still leaves the plain screenshot return format, the effect of maxWidth, and the player/server scoping unexplained for a six-parameter tool.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry the parameter burden. It explains method, baseline, and saveBaseline semantics well (save-on-first-use, comparison threshold of 0.5%), but player, server, and maxWidth are never mentioned, leaving half the parameters undocumented anywhere.

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?

Opens with a specific verb+resource ("Screenshot the game") and immediately disambiguates the two capture paths, local window with NUI versus bridge capture for remote clients. That is clear enough to separate it from siblings like nui_snapshot or game_get_state, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

Gives concrete selection criteria for the method values: auto/window when the local FiveM window (including NUI) is what you want, game when the target is a remote client or NUI is irrelevant. It stops short of stating when not to use this tool or pointing at a sibling for the non-screenshot case.

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