Skip to main content
Glama
Sign In
moreplay

moreplay

by JastinXyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

screenshot

Capture and save the Android screen as a JPEG, returning its file path; optionally display it and extract small crops from specified refs without saving.

Instructions

Save a JPEG of the screen and return its path. show=true to see it too.

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": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNofile name (evidence folder) or a path
refsNoinstead: small crops of these @refs (e.g. icon), nothing saved
showNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the core behavior: saving a JPEG, returning its path, and optionally displaying it, but it omits whether files are overwritten, where they are saved, and how the refs crop mode differs. The core behavior is adequate, but important side-effect details are missing.

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?

The description is two short sentences with the main action front-loaded and no wasted wording. Every sentence contributes directly to understanding the tool.

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?

The definition is minimally complete for the default screenshot-and-save behavior, and the schema covers name and refs. However, the description does not mention the refs crop mode that saves nothing, nor does it clarify file overwrite behavior, leaving gaps for an agent invoking non-default modes.

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 67%, and the schema itself documents name and refs meaningfully. The description adds meaning for show, which has no schema description, but does not add much beyond the schema for name or refs.

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 and resource: it saves a JPEG of the screen and returns the path. It is clear what the tool does, but it does not distinguish itself from sibling tools such as observe, act, or flow.

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?

The only usage guidance is 'show=true to see it too,' which explains a parameter rather than when to use this tool instead of observe, act, or flow. There is no explicit when-to-use or when-not-to-use guidance.

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