Skip to main content
Glama
Sign In
shapeyourphone

shapeyourphone

by rachitkj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

launcher_rules

Read-only

Displays time-based home screen rules and marks which ones are active now, so you can review schedules and see what applies at the current time.

Instructions

Time rules on the home screen (● = active now).

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

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

C2.7/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, closed-world operation. The description adds one behavioral detail—that '● = active now' in the output—but does not clarify whether it lists all rules, a subset, or how rules are formatted beyond that marker.

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 definition is extremely short, which is efficient, but it is a sentence fragment without a clear action verb. Its brevity comes at the cost of structural clarity rather than reflecting purposeful concision.

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

Completeness2/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 the description should carry more of the burden of explaining what the tool returns. Aside from the active-rule marker, it omits whether this lists rules, fetches rule details, or how results are organized—leaving a meaningful gap for an agent selecting among many launcher_* siblings.

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 fully described as the adb serial needed when several phones are connected. The description adds no parameter-specific meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as 'time rules on the home screen,' which is more specific than the tool name alone, but it provides no verb (list, get, manage, apply) to say what the tool actually does with those rules. An agent must infer from the readOnly annotation that this is a retrieval operation.

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 guidance about when to use this tool, what it should be used instead of, or how it relates to siblings like launcher_get_config, launcher_status, or launcher_edit. The agent receives no explicit usage context.

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