Skip to main content
Glama
Sign In
shapeyourphone

shapeyourphone

by rachitkj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launcher_edit

Edit an Android home screen by app name: hide, unhide, dock, rename, theme, set gestures, pause apps, or apply time rules. Changes are previewed and require owner approval before applying.

Instructions

Small home-screen edits by app name. command + args mirror the CLI, e.g. hide ['Instagram','--days','weekdays','--from','09:00','--to','18:00'] · unhide ['Instagram'] · search-only ['TikTok'] · dock ['WhatsApp','Spotify'] · home-apps ['Maps','--style','grid'] · theme ['--icons','grayscale','--background','wallpaper'] · gesture ['doubleTap','Spotify'] · rename ['WhatsApp','Chats'] · pause ['Instagram','--seconds','10'] · rule-remove ['Night'] · usage-access [].

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": {
      "command": "<command>"
    },
    "name": "launcher_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
deviceNoadb serial, only needed when several phones are connected
commandYes
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.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world, so the safety bar is partly covered. The description adds real behavioral color through the example flags (hide with --days weekdays --from 09:00 --to 18:00 implies scheduled hiding; pause implies a timed suspension), but it never says whether these edits are reversible, what they overwrite, or that omitting owner_approved yields a preview rather than an applied change.

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 purpose is front-loaded in the first sentence, which is good. But the rest is a single run-on sentence of dot-separated examples that is dense and scannable only with effort; a short list or grouping by read-vs-mutate would carry the same information more clearly.

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, a mutating tool, and 50% schema description coverage, the description should explain what a call returns and how the preview/apply handshake works. It covers the command vocabulary well but leaves the result of the call and sibling disambiguation to inference.

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

Parameters4/5

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

The 'args' parameter is an undescribed free-form string array in the schema, and the description is the only place that gives it meaning by mapping arrays to each command (hide, unhide, search-only, dock, theme, gesture, rename, pause, rule-remove, usage-access). It falls short of systematic documentation—the examples are illustrative rather than exhaustive, and optional flags for many commands remain unstated.

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?

States a specific resource and action ('Small home-screen edits by app name') and enumerates all eleven commands with representative arguments, so an agent can tell what class of operation it performs. It does not, however, distinguish itself from close siblings like launcher_set_config, launcher_rules, or launcher_preview, which appear to overlap.

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: nothing says when to pick launcher_edit over launcher_set_config, launcher_rules, or launcher_preview, nor when a launcher_rollback is appropriate afterwards. The preview/approval workflow is only implied by the schema's owner_approved field, not by 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