mobilerun-mcp

Capabilities

capabilities

Retrieve the backend, platform, and supported actions of a target device. This helps AI agents determine compatible operations for automation.

Instructions

Backend, platform and the actions this device supports.

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

Input Schema

Name	Required	Description	Default
`device`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It implies an informational query but does not state that it is read-only, whether it has side effects, or what permissions it requires. This is a significant gap for an agent deciding whether invoking it is safe.

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

Conciseness3/5

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

The description is short and economical, so it is not bloated. However, it is a sentence fragment rather than a structured, front-loaded explanation, and its brevity comes at the cost of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. Still, with no annotations, 0% parameter coverage, and no usage guidance, the description is incomplete for helping an agent invoke the tool correctly in the context of many sibling tools.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional 'device' parameter, and the description does not explain what the parameter accepts or how omitting it affects the result. The phrase 'this device' hints at device scoping but does not add real semantic meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the information categories ('Backend, platform and the actions this device supports'), which gives some sense of what the tool returns. However, it does not use a specific verb or resource action, and it does not distinguish this tool from siblings such as 'supports'. The purpose remains somewhat vague.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tool is the appropriate alternative. The description provides no context for selecting it over related tools like 'supports' or 'get_device_status'.

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

Deploy Server