Skip to main content
Glama
Sign In
shapeyourphone

shapeyourphone

by rachitkj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

doctor

Read-only

Verifies adb availability, detects the connected Android phone, and checks the Shape launcher so you can diagnose setup issues before making device changes.

Instructions

Check adb, the connected phone and the Shape launcher.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoadb serial, only needed when several phones are connected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the "Check" wording is consistent with it. The description adds the scope of what is inspected, but says nothing about what the check reports, whether it can fail loudly, or what the agent should do with the result.

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?

A single economical sentence with the action front-loaded and the three targets grouped. It wastes nothing, though it is arguably too terse for a diagnostic entry point.

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?

With no output schema, the description carries the burden of explaining what a 'doctor' returns, and it does not — the agent only knows which subsystems are inspected, not the shape or content of the report. The scope list partially compensates, making it adequate but with a clear gap for a diagnostic tool.

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 100% and the single 'device' parameter is already documented in the schema as an adb serial needed only with multiple phones. The description adds no further meaning, so the baseline of 3 applies.

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 gives a concrete verb ("Check") and enumerates three specific targets: adb, the connected phone, and the Shape launcher. That distinguishes it reasonably well from siblings like 'phones' or 'launcher_status', though it never explicitly states how it differs from those narrower status tools.

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 when-to-use guidance, no mention of prerequisites (e.g., run before 'init' or when something seems broken), and no reference to alternatives such as 'phones' or 'launcher_status'. The agent must infer that this is a pre-flight/troubleshooting diagnostic from the name 'doctor' alone.

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