MobAI MCP Server

Official

by MobAI-App

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

save_screenshot

Save a full-quality PNG screenshot to disk for high-resolution reporting, debugging, or sharing.

Instructions

Save a full-quality PNG screenshot to disk. Use this when you need a high-quality image for reporting, debugging, or sharing — not for LLM processing (use get_screenshot instead).

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": {
      "device_id": "<device_id>"
    },
    "name": "save_screenshot"
  }
}

Input Schema

Name	Required	Description
`device_id`	Yes	Device ID
`path`	No	Directory to save screenshot to (supports ~/). Defaults to OS temp directory.
`name`	No	Optional filename (without .png extension)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.1Jun 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions saving to disk and the default directory, but does not disclose potential side effects (e.g., overwriting behavior), required permissions, or return value. This is adequate but not comprehensive.

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 consists of two concise sentences with no superfluous words. The primary action ('Save') is front-loaded, and the alternative guidance is efficiently integrated.

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 tool has 3 parameters, no output schema, and no annotations. The description does not mention the return value (e.g., file path or success status) or handle error cases. While adequate for a simple save operation, some contextual details are missing.

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 description coverage is 100%, so the schema already documents all 3 parameters clearly. The description does not add any extra parameter-level details beyond what the schema provides, earning the baseline score of 3.

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 explicitly states 'Save a full-quality PNG screenshot to disk.' It identifies the verb (save), resource (screenshot), format (PNG), and quality (full-quality), clearly distinguishing it from the sibling tool get_screenshot.

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?

The description explicitly states when to use this tool ('when you need a high-quality image for reporting, debugging, or sharing') and when not to use it ('not for LLM processing'), directly naming the alternative tool get_screenshot.

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