Skip to main content
Glama
Apple HIG MCP Server

Apple HIG MCP Server

by Amo643

search_hig

Read-onlyIdempotent

Locate Apple Human Interface Guidelines topics, titles, descriptions, and categories by keyword, with an optional category filter, to find relevant design guidance.

Instructions

Search across Apple Human Interface Guidelines topics, titles, descriptions, and categories in real-time.

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": {
      "query": "<query>"
    },
    "name": "search_hig"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe search query or keyword (e.g. "liquid glass", "buttons", "dark mode", "hit target", "typography").
categoryNoOptional category filter (e.g. "Foundations", "Components", "Platforms", "Patterns", "Inputs").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description contributes only that results are retrieved "in real-time" (a live remote lookup); it says nothing about ranking, result caps, pagination, or empty-result behavior, which would be genuinely additive.

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 front-loaded sentence with the resource and the searched field set stated immediately, and no filler wording. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, low-complexity read tool with full annotation coverage, the definition is serviceable but leaves a real gap: there is no output schema, so the description is the only place to say what a result contains (title, category, snippet, link) or how many come back. An agent can invoke it correctly, but cannot anticipate the response shape.

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 both query and category are documented in the schema with concrete examples ("liquid glass", "Components"). The description adds no additional meaning such as matching rules, multi-word behavior, or whether category must match an exact listed value, so the baseline of 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 names a specific verb ("Search") and a specific resource (Apple Human Interface Guidelines), and narrows the searched fields to topics, titles, descriptions, and categories, which clearly separates it from get_guideline or list_categories. It never explicitly names those siblings as alternatives, so it falls short of a 5.

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: an agent can infer this is the keyword-lookup entry point while get_guideline fetches a specific doc, but the description never states when to choose one over the other. "In real-time" hints that results are fetched live rather than from a static index, but no conditions or exclusions are given.

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