Skip to main content
Glama
Apple HIG MCP Server

Apple HIG MCP Server

by Amo643

get_redesign_checklist

Read-onlyIdempotent

Generate an actionable Apple HIG checklist to redesign and polish apps, helping them feel native and refined across iOS, macOS, visionOS, or all platforms.

Instructions

Generate an actionable Apple HIG checklist for redesigning and polishing apps to feel native and refined.

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

Input Schema

NameRequiredDescriptionDefault
platformNoTarget platform for the checklist (default: "all").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds only that the output is an 'actionable checklist', without disclosing how items are grouped, whether output is static per platform, or how granular it is, so it adds modest value beyond annotations.

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?

A single well-formed sentence with the purpose and scope front-loaded and no filler. Every clause ('redesigning and polishing', 'feel native and refined') contributes to scoping the output.

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?

For a one-optional-parameter generator with full annotation coverage, the description gives enough to call it correctly. The remaining gap is the shape of the returned checklist, which is minor absent an output schema but would have been a useful addition.

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 100%, and the single enum parameter with its default is fully documented in the schema. The description adds no meaning about how platform selection changes the checklist content, so baseline 3 applies.

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 uses a specific verb ('Generate') and a specific resource ('Apple HIG checklist') and scopes it to redesign/polish work, which an agent can distinguish from retrieval-style siblings like get_guideline or search_hig. It stops short of naming those siblings explicitly, so differentiation requires a small inference.

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 wording 'for redesigning and polishing apps' implies the usage context, but there is no explicit when-to-use versus when-to-use-a-sibling guidance and no exclusions. An agent must infer that this is the aggregate/checklist path while the other tools fetch individual guidelines.

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