Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

get_reference_guide

Read-onlyIdempotent

Open the official provider workflow for an upstream reference, returning vetted links and native MCP handoff instructions for Details, Mobbin, and design-system sources.

Instructions

Open the official provider workflow for an upstream reference. Returns vetted links and native MCP handoff instructions for Details, Mobbin and design-system sources.

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": {
      "provider": "<provider>"
    },
    "name": "get_reference_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
topicNo
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.7/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 carried by structured data. The description adds real value by saying the result contains vetted links plus native MCP handoff instructions, which tells the agent the response is instructional rather than raw content. It does not disclose behavior for unsupported or missing references, or whether unlisted providers error or fall back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the return value stated up front and no filler. It is efficiently sized, though the first sentence's 'open the official provider workflow' phrasing costs clarity for the space it saves.

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

Completeness2/5

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

With three parameters (one required enum of ten values), zero schema descriptions and no output schema, the definition should explain the provider values and the roles of url and topic. It leaves an agent unable to construct a correct call for most enum values, and offers no routing guidance among the many retrieval siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only names three of the ten enum values (Details, Mobbin, design-system sources), leaving granola, linear, govuk, stripe, radix, instrument, arena and pentagram unexplained. The `url` and `topic` parameters receive no mention at all, so the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb phrase 'Open the official provider workflow for an upstream reference' is metaphorically vague — it's unclear whether this launches something, fetches a document, or returns instructions. The second sentence does clarify the deliverable ('vetted links and native MCP handoff instructions'), but the purpose is not sharply distinguished from siblings like get_vault_resource or read_inspiration_source, which sound like overlapping retrieval operations.

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?

There is no guidance on when to call this versus alternatives, no prerequisites, and no exclusions. An agent must guess whether this supersedes get_inspiration, read_inspiration_source, or get_design_pack for a given retrieval need.

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