Skip to main content
Glama
Sign In
shapeyourphone

shapeyourphone

by rachitkj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

init

Prepare a new Android phone by saving its profile and full backup, then create the preferences file that guides approved, undoable changes.

Instructions

First step with a new phone: save its profile and a full backup, create its preferences file.

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

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

A3.7/5.0
Behavior3/5

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

Annotations declare a non-destructive, non-readonly, closed-world write, and the description usefully enumerates the artifacts it produces (profile, backup, preferences file). It does not say where those artifacts are stored, how large the backup is, or what happens on a second run against an already-initialized phone, which is the main behavioral risk for this mutation.

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?

A single front-loaded sentence that leads with the trigger condition ("first step with a new phone") before listing the three artifacts created. No filler or redundant restatement of the tool name.

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?

For a one-optional-parameter mutation tool with no output schema, the description covers the trigger and the side effects adequately. It leaves open idempotency (rerunning on an initialized phone) and where the backup lands, which an agent would want to know before invoking.

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 optional `device` parameter is already documented in the schema as an adb serial needed only with multiple phones. The description adds nothing beyond the schema, so baseline 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 states a concrete verb set (save profile, full backup, create preferences file) on a specific resource (a new phone), and the phrase "first step with a new phone" frames it as an onboarding action. It does not name any sibling it is distinct from, though the setup framing implicitly separates it from tools like restore_everything or preferences_write.

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

Usage Guidelines4/5

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

"First step with a new phone" gives clear when-to-use guidance and implies ordering relative to the rest of the playbook. It does not state exclusions or what to do if the phone is already initialized, so the bar for a 5 is not met.

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