Skip to main content
Glama
Sign In
shapeyourphone

shapeyourphone

by rachitkj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launcher_install

Install the Shape launcher and set it as the phone’s home screen while keeping the existing launcher installed.

Instructions

Install the Shape launcher and make it the home screen (the old launcher stays installed).

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

Input Schema

NameRequiredDescriptionDefault
deviceNoadb serial, only needed when several phones are connected
owner_approvedNotrue only after the phone's owner saw the preview and agreed. Omit to get a preview.

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?

The annotations already declare readOnlyHint=false and destructiveHint=false, and the description reinforces this usefully by noting the old launcher stays installed and that the default home screen is switched. However, it omits the two-phase consent flow and the availability of launcher_rollback as an escape hatch, which are the behaviors an agent most needs to know before mutating device state.

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 with the action and the consequential side effect, plus a tight parenthetical that preempts the obvious 'will this break my phone?' question. Nothing is wasted.

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 device-mutating install with a preview/approval gate and no output schema, the description should mention that calling it without approval yields only a preview and that rollback exists. Annotations and the full-coverage schema cover enough that an agent can still call it, but the workflow context is incomplete.

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% and both parameters are well documented in-schema, including the 'omit to get a preview' semantics of owner_approved. The description adds no parameter meaning beyond that, so the 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 uses a specific verb and resource ('Install the Shape launcher') and states the key side effect ('make it the home screen'), so the agent knows exactly what this does versus siblings like launcher_preview or launcher_uninstall. It does not explicitly name which sibling to use instead, which keeps it short of a 5.

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 statement of when to call this rather than launcher_preview, launcher_set_config, or launcher_uninstall, and no mention of prerequisites beyond the parenthetical about the old launcher. The critical gating condition (preview first, then owner approval) lives only in the parameter schema, not the description.

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