home-screen-mcp

Overview Schema Source Related Servers Discussions Admin

place_at

Places a Home Screen item at a specific page, row, and column while preserving empty space around it; surrounding items automatically flow to make room.

Instructions

Put an item in an exact spot (row 1-6, column 1-4) on a page, leaving empty spaces around it, like dragging it to an empty spot on the iPhone. Other items flow around it.

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": {
      "item_id": "<item_id>",
      "page": "<page>",
      "row": "<row>",
      "column": "<column>"
    },
    "name": "place_at"
  }
}

Input Schema

Name	Required	Description	Default
`row`	Yes
`page`	Yes
`column`	Yes
`item_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key mutation effect: empty spaces are left around the item and other items flow around it. However, it omits what happens if the target spot is occupied, permission requirements, idempotency, and page-boundary behavior.

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 sentences, front-loaded with the placement action and followed by the resulting layout behavior. The iPhone drag analogy is useful, though slightly informal; there is no wasted repetition of schema details.

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?

An output schema exists, so return values need not be explained. For a four-required-parameter mutation tool with no annotations, the description covers core placement behavior but leaves collision handling, authorization, and page constraints unstated.

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 0%, so the description must compensate. It adds meaningful bounds for row (1-6) and column (1-4) and implies item_id and page meanings, but leaves page range, item_id format, and coordinate exclusivity undocumented.

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 verb and resource: 'Put an item in an exact spot ... on a page.' The exact row/column placement and flow behavior distinguish it from looser arrangement siblings, though it does not name any alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it: precise placement that leaves empty spaces, analogous to dragging to an empty iPhone spot. It does not explicitly contrast with move, arrange, swap, or close_gaps, nor state exclusions.

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