home-screen-mcp

Overview Schema Source Related Servers Discussions Admin

sort_folder_contents

Sorts app icons inside each Home Screen folder alphabetically A–Z, simplifying iPhone or iPad layout organization before applying changes over USB.

Instructions

A-Z inside every folder.

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

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

C2.3/5.0

Behavior2/5

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

No annotations at all, so the description carries the full burden and delivers almost nothing: it does not say this is a mutating reorder, whether it is undoable (an undo sibling exists), whether it affects all folders or only the current one, or what permissions it needs. The phrase "inside every folder" is the only real behavioral signal — scope — which lifts it above a 1.

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

Conciseness2/5

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

It is short, but this is under-specification rather than conciseness — a five-word fragment that front-loads nothing and omits the verb entirely. Length is fine; content density is not.

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, but for an unannotated mutation tool the description should still cover reversibility, scope, and side effects. None of that is present, leaving the agent to guess.

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, so baseline is 4; there is nothing the description could add. It does at least confirm the operation applies across every folder rather than a specified one.

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

Purpose2/5

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

"A-Z inside every folder" largely restates the name: sort_folder_contents becomes "A-Z" plus "inside every folder." There is no verb (sort, order, arrange) and no differentiation from the sibling sort_alphabetically, so an agent cannot tell which of the two it should pick.

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?

No when-to-use, when-not-to-use, or prerequisite information is given. With sort_alphabetically sitting right next to it in the sibling list, the absence of any routing guidance is a real gap.

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