home-screen-mcp

Overview Schema Source Related Servers Discussions Admin

apply

Writes an explicitly approved Home Screen draft to iPhone or iPad using the diff token, backing up first and verifying the result after the change.

Instructions

Write the draft to the iPhone. Only call when the user explicitly asked to apply this draft. Needs the apply_token from the latest diff. Backs up first and verifies after.

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": {
      "apply_token": "<apply_token>"
    },
    "name": "apply"
  }
}

Input Schema

Name	Required	Description	Default
`apply_token`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: it backs up before writing and verifies afterward, implying a recoverable, checked mutation. It leaves out what happens if verification fails and whether the write replaces the entire phone layout or merges, which matters given the sibling 'restore'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, action front-loaded, followed by the call gate, the prerequisite, and the safety behavior. No wasted words and no repetition of the schema.

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

Completeness5/5

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

For a single-parameter mutation with no annotations and an output schema that covers return values, the description supplies the gating rule, the token provenance, and the backup/verify safety story. That is sufficient for an agent to decide whether and how to call it.

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?

Schema coverage is 0%, so the description must compensate, and it does by explaining that apply_token must come from the latest diff rather than being any arbitrary string. That provenance detail is exactly the missing semantics an agent needs; format or expiry of the token is still 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 concrete verb and resource plus a destination: 'Write the draft to the iPhone.' It implicitly distinguishes itself from the sibling 'diff' by requiring the token from the latest diff, so an agent can tell it is the commit step rather than the preview step.

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

Usage Guidelines4/5

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

Gives an explicit gating condition: 'Only call when the user explicitly asked to apply this draft,' which is a clear when-not as well as a when. It also names the prerequisite (apply_token from the latest diff), though it does not name an alternative for the case where the user merely wants a preview.

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