Skip to main content
Glama
Apple HIG MCP Server

Apple HIG MCP Server

by Amo643

get_design_resources

Read-onlyIdempotent

Get direct download and official links to Apple Design Resources, including Figma kits, SF Symbols, app icon templates, and device bezels for design work.

Instructions

Get direct download and official links to Apple Design Resources (Figma kits, SF Symbols, app icon templates, device bezels).

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_design_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered elsewhere. The description's added value is modest: it indicates the response consists of direct download and official links, which matters given there is no output schema, but it says nothing about whether the list is static/curated, freshness, or whether the links are region- or auth-gated.

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 named first and the returned artifact types in a compact parenthetical. Every clause carries information and there is no filler.

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-argument, read-only lookup with no output schema, the definition covers purpose and result shape adequately. It stops short of describing the structure of the returned links or how many resources to expect, which would fully close the loop in the absence of an output schema.

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, so there is nothing for the description to disambiguate; baseline of 4 applies. No parameter-related claims are made or needed.

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?

Uses a specific verb ("Get") with a concrete resource ("Apple Design Resources") and enumerates the artifact types returned (Figma kits, SF Symbols, app icon templates, device bezels). It does not explicitly contrast itself with siblings like search_hig or get_guideline, but the resource is distinct enough that confusion is unlikely.

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 it should call this when it needs design asset links. There is no explicit when-to-use statement, no when-not-to-use, and no mention of the sibling tools that might compete for the same intent (e.g. get_guideline for guidance rather than assets).

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