Skip to main content
Glama
Sign In
apple-design-mcp

apple-design-mcp

by rncrosby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get HIG page

hig_get
Read-onlyIdempotent

Fetch a specific Apple Human Interface Guidelines page as Markdown. Provide a slug, title, path, or URL to get the content.

Instructions

Fetch one Human Interface Guidelines page as Markdown. Pass a slug (color, buttons), title, path, or developer.apple.com URL.

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

Input Schema

NameRequiredDescriptionDefault
topicYesSlug, title, path, or URL, e.g. 'buttons', 'designing-for-ios', or '/design/human-interface-guidelines/color'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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, openWorldHint, and idempotentHint, covering safety. The description adds the output format (Markdown) and clarifies accepted input types, which is useful but does not go beyond basics like error behavior, acceptable given the 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?

Two sentences with the core action front-loaded and the input specification clearly stated in the second sentence. No redundant or vague language.

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 single-parameter read-only tool with no output schema, the description covers what it does, what it returns, and how to specify the topic. It omits error handling details, but those are minor for this simple scope.

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?

The schema already describes the topic parameter with examples and coverage is 100%, so the baseline is 3. The description adds mention of developer.apple.com URLs and repeats slug examples, but adds little new semantic meaning beyond the schema.

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 clearly states 'Fetch one Human Interface Guidelines page as Markdown', specifying the verb and resource. It does not explicitly differentiate from sibling tools like hig_search or hig_toc, but the purpose is unambiguous.

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 description instructs to pass a slug, title, path, or developer.apple.com URL, which guides input usage. However, it does not mention when to use this tool over alternatives, leaving the choice implied (e.g., use when you have a specific page identifier).

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

Deploy Server

Other Tools