Swipium

Overview Schema Source Related Servers Discussions Admin

Capture a screenshot

qa_screenshot

Captures a QA screenshot for a mobile test session, saves it as a session artifact, and returns a swipium:// URI for reports; password/OTP screens are withheld unless forced.

Instructions

Save a screenshot as a session artifact and return its swipium:// URI. Withheld on password/OTP screens unless force:true. Counts against the screenshot budget. inline:true also returns the image (JPEG, long edge 1568 px, scale in the text) for clients that can see images.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "qa_screenshot"
  }
}

Input Schema

Name	Required	Description
`force`	No
`inline`	No	Also return the image inline (the result then has no structuredContent).
`reason`	No	What it documents (shown in qa_report).
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations (which only say non-read-only, non-destructive, non-idempotent) by disclosing the privacy gate on password/OTP screens, the quota consumption, and exactly what inline returns (JPEG, long edge 1568 px, scale in text). This is the kind of behavior an agent cannot get from structured fields.

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?

Four short sentences, front-loaded with the action and return value, then conditions and modes. Dense and mostly waste-free; the 'Counts against the screenshot budget' fragment is terse but earns its place as a quota warning.

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?

A mutation-style artifact-creating tool with no output schema is well covered: it explains the returned URI, the inline image shape, privacy withholding, and quota cost. It could say what happens to the result when the screen is withheld, but nothing essential for calling it is missing.

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 coverage is 50% (inline and reason documented, force and sessionId bare). The description compensates by explaining what force bypasses and what inline adds over the schema's note about missing structuredContent, leaving only the obvious sessionId unexplained.

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 verb and resource ('Save a screenshot as a session artifact') plus the return value ('swipium:// URI'). The URI mention implicitly routes the agent to the artifact-retrieval sibling, and no other sibling does screenshot capture.

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 clear conditional guidance: withheld on password/OTP screens unless force:true, counts against the screenshot budget, and inline:true only for clients that can see images. It stops short of naming an alternative tool for auditing versus documenting, but the preconditions are explicit.

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