Skip to main content
Glama
Apple HIG MCP Server

Apple HIG MCP Server

by Amo643

get_guideline

Read-onlyIdempotent

Fetches the complete, live Markdown content of any Apple Human Interface Guidelines topic from developer.apple.com, so you can retrieve official design guidance by topic slug, name, or keyword.

Instructions

Fetch the complete, live Markdown content of any Apple HIG topic directly from developer.apple.com.

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": {
      "topic": "<topic>"
    },
    "name": "get_guideline"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic slug, name, or keyword (e.g. "materials", "buttons", "color", "dark-mode", "layout", "typography", "designing-for-macos", "accessibility").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely new context by saying the content is "live" (network fetch of current upstream content) and "complete Markdown" (full document rather than a snippet), but says nothing about failure behavior for an unknown slug or caching.

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 no filler, and the key qualifiers (complete, live, Markdown, source) are packed efficiently up front.

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?

With no output schema, the description correctly characterizes the return value as complete live Markdown content, which is the main thing an agent needs to know. It stops short of covering error behavior for an unrecognized topic, which is a minor gap for a one-parameter fetch tool.

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 coverage is 100% and the topic parameter's description already lists slug, name and keyword forms with eight concrete examples. The description adds nothing beyond that, so the 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?

States a specific verb and resource ("Fetch ... the complete, live Markdown content of any Apple HIG topic") and names the source, developer.apple.com. It is clearly distinguishable from a search tool, though it does not explicitly differentiate itself from siblings like list_topics or get_design_resources.

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 guidance is given: nothing says to call this after list_topics to drill into a specific topic, nor when to prefer search_hig for keyword lookups instead. Usage is only inferable from the tool name and verb.

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