home-screen-mcp

Overview Schema Source Related Servers Discussions Admin

show_layout

Displays the current iPhone or iPad Home Screen layout, including dock, pages, App Library apps, folders, and widget sizes, so you can inspect structure before sorting or rearranging.

Instructions

The current draft: dock, every page and the App Library-only apps, as {id, name} items (folders carry their contents, widgets their size).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose useful structure — items are {id, name}, folders nest their contents, widgets report size — which implies a read-only inspection with no mutation. It stops short of stating that the draft is unmodified, whether a draft must exist, or anything about failure modes.

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?

A single sentence with parenthetical detail and no filler. The front-loaded 'The current draft:' frames the subject immediately, though the telegraphic register and absence of a leading verb slightly hurt scannability.

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?

With an output schema present, the description need not document return values, yet it still sketches the item shape, which helps. For a zero-parameter read tool this is close to complete; only the missing when-to-use framing keeps it from a 5.

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 tool takes zero parameters (schema coverage 100%, empty properties object), so there is nothing for the description to disambiguate. Baseline 4 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 names the resource (the current draft) and enumerates its scope: dock, every page, and App Library-only apps. However, it opens with a bare noun phrase rather than a verb, never says 'show' or 'returns', and offers no differentiation from siblings like render_preview, diff, or read_phone.

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 on when to call this versus alternatives such as render_preview (visual) or diff (comparison), nor any stated precondition. The agent must infer usage purely from the name and the content enumeration.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.