Skip to main content
Glama
Apple HIG MCP Server

Apple HIG MCP Server

by Amo643

list_categories

Read-onlyIdempotent

Lists all top-level Apple Human Interface Guidelines categories with topic counts, helping you discover available design topics before searching or generating checklists.

Instructions

List all top-level categories in Apple Human Interface Guidelines with topic counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description need not restate safety. It does add genuinely new information by disclosing the return content (categories plus topic counts), which matters since there is no output schema; the only gap is that "all" is not qualified regarding pagination or truncation.

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 sentence with the resource and the returned payload front-loaded and no filler. Every clause carries information an agent needs.

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 zero-parameter read tool with full annotation coverage, the description supplies the one thing structured fields cannot: what the call returns (categories with topic counts). The only shortfall is the missing pointer to list_topics and search_hig, which would have made the browsing sequence explicit.

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 and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. Baseline for a parameterless tool is 4, and the description correctly avoids inventing filtering options that do not exist.

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?

"List all top-level categories in Apple Human Interface Guidelines with topic counts" names a specific verb (list), a specific resource (top-level categories), and the payload (topic counts). It is clear on its own, but it never contrasts with the sibling list_topics, so the boundary between top-level categories and topics must be inferred from the wording alone.

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?

Usage is only implied: "top-level" suggests this is the entry point for browsing before drilling into a category, but the description gives no explicit when-to-use, no prerequisites, and does not name list_topics or search_hig as alternatives. An agent can guess the intended position in the workflow but is not told.

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