Skip to main content
Glama
Sign In
shapeyourphone

shapeyourphone

by rachitkj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launcher_get_config

Read-only

Retrieves the current Android home-screen configuration as JSON so agents can inspect the launcher layout before changes; optionally specify a connected device by adb serial.

Instructions

The home-screen config currently on the phone (JSON). Format: docs/launcher-config.md.

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_get_config"
  }
}

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. The description adds that the value reflects the phone's current live state and that the payload is JSON documented in docs/launcher-config.md, which is modest but real added context; it says nothing about behavior when no device is connected or when several are.

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?

Two terse fragments with zero filler, and the resource identity is front-loaded. The style is telegraphic rather than prose, but nothing is wasted.

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

Completeness4/5

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

There is no output schema, so pointing at docs/launcher-config.md for the JSON format is the right compensating move for a single optional parameter and a read-only tool. The definition is adequate to call it correctly, though it could note the no-device default behavior.

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 fully documented in the schema as an adb serial needed only with multiple phones. The description adds nothing beyond that, 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?

Names a concrete resource ('home-screen config') and states it is the config currently on the phone, returning JSON. The 'get' semantics are clear enough to separate it from launcher_set_config and launcher_edit, though the description never explicitly contrasts with siblings.

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?

No when-to-use guidance, no prerequisites, and no routing to alternatives such as launcher_status or launcher_preview. An agent must infer from the name that this is the read-side of the launcher family.

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