podium-mcp

Overview Schema Source Related Servers Discussions Admin

screenshot

Take a screenshot of an iOS simulator by supplying its UDID. The image is saved as a .png or .jpg file, returning the file path and byte size.

Instructions

Takes a screenshot of an iOS simulator. Returns the saved file path and byte size. Does NOT return base64 to keep payload small. saveTo defaults to a .png file in os.tmpdir().

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": {
      "udid": "<udid>"
    },
    "name": "screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`udid`	Yes	Simulator UDID
`saveTo`	No	Destination file path (must end .png or .jpg). Defaults to a tmp file.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description discloses the output format and design decision to avoid base64, but omits details like whether it overwrites existing files, permissions needed, or if the simulator must be booted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action, and every sentence adds value without redundancy.

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?

Given no output schema, the description explains the return values (file path and byte size) and default behavior. It could mention error conditions or prerequisites, but is still mostly complete.

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 100%, but the description adds the default save location details (os.tmpdir()), which goes beyond the schema's 'Defaults to a tmp file.' This extra context helps the agent.

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?

The description clearly states the tool takes a screenshot of an iOS simulator, which is a specific verb+resource. Among siblings like inspect_screen, this tool uniquely captures a full screenshot image.

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

Usage Guidelines3/5

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

The description provides context (returns file path, not base64, default save location) but does not explicitly state when to use this tool versus alternatives like inspect_screen or tap_on. Usage is implied rather than explicit.

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