Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

get_design_pack

Read-onlyIdempotent

Retrieve a design pack by ID to read its appearance tokens, design principles, and reference IDs for interface styling and remixing.

Instructions

Read a pack’s appearance tokens, principles and reference IDs.

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": {
      "id": "<id>"
    },
    "name": "get_design_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds useful scope by enumerating what is returned (tokens, principles, reference IDs), but says nothing about behavior when the pack is missing or invalid, or about size/response shape.

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?

One front-loaded sentence with no filler, and the returned content is stated up front. It is efficient, though its brevity leaves the caller without routing or parameter context.

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 simple one-parameter read tool with full annotations, the description covers what comes back reasonably well. It is still thin on how to obtain a valid pack ID and on failure behavior, which matters since there is no output schema to fall back on.

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%, so the single required 'id' parameter has no documented meaning anywhere except the possessive "a pack's," which weakly implies it is a pack ID. No format, source of valid IDs, or constraints (maxLength 120) are explained in the description.

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 ("Read") and resource (a pack) plus the payload it returns: appearance tokens, principles, and reference IDs. That return-content detail helps distinguish it from list_design_packs, though it doesn't name or contrast any sibling explicitly.

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 when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that this is the single-pack retrieval counterpart to list_design_packs, and must infer that 'id' refers to a pack identifier rather than a token or reference ID.

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