home-screen-mcp

by worldsavepoint

Overview Schema Source Related Servers Discussions Admin

Python

Local

sort_alphabetically

Sorts iPhone or iPad Home Screen folders and loose apps A-Z, leaving page 1 unchanged by default.

Instructions

A-Z sort of folders and loose apps. Page 1 is left alone by default.

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

Input Schema

Name	Required	Description	Default
`folders_first`	No
`keep_first_page`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that page 1 is untouched by default and that folders and loose apps are sorted, but it does not say whether the operation is reversible, whether folder contents are affected, or what side effects occur on the home screen layout.

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?

Two short sentences with no wasted language, and the core sorting behavior is front-loaded before the default page behavior. It is appropriately sized for the amount of information it chooses to convey.

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?

An output schema exists, so return values need not be explained. However, with no annotations and 0% schema description coverage, the description is too thin for a layout-mutating tool: it omits side effects, reversibility, and meaningful parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 explain both parameters. 'Page 1 is left alone by default' partially explains keep_first_page, but folders_first is not explained at all beyond its name, leaving the grouping behavior ambiguous.

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?

The description states a specific verb and resource: an A-Z sort of folders and loose apps. This distinguishes it reasonably well from siblings like sort_by_color and sort_folder_contents, though it does not explicitly name or contrast those alternatives.

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?

It gives no guidance on when to use this tool versus sort_by_color, sort_folder_contents, arrange, or other layout tools. The only usage-related detail is the default behavior of leaving page 1 alone.

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