Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

get_inspiration

Read-onlyIdempotent

Inspect a selected design reference to pull its PNG or seven ordered frames plus a versioned source manifest; request metadata only when images are not needed.

Instructions

Inspect a selected reference. Returns an actual PNG or seven ordered frames, plus a versioned source manifest. Set includeImages to false for metadata only.

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

Input Schema

NameRequiredDescriptionDefault
idNoAtlas ID, slug, copied Remix text, or gallery URL.
slugNo
includeImagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral information: the response is either a binary PNG or seven ordered frames, accompanied by a versioned source manifest, and images can be suppressed. That return-shape disclosure is valuable given there is no output schema. It does not mention size limits, caching, or failure modes for an unresolvable id.

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?

Three short sentences, front-loaded with the action and the return shape, ending with the one actionable parameter hint. No filler or repetition of the tool name.

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?

With no output schema, the description correctly spends its space describing what comes back (PNG vs. seven frames, versioned manifest) and how to opt out of images. What remains thin is the selection model for a tool with zero required parameters and an unexplained second identifier field.

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 coverage is only 33%, so the description must carry weight; it does define the includeImages toggle (false = metadata only), which is the most consequential flag. However, the slug parameter is undocumented everywhere, and the description never explains the relationship between id and slug, nor what happens when neither is supplied given zero required parameters.

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?

"Inspect a selected reference" gives a concrete verb and resource, and the follow-up sentence pins down the payload (PNG or seven ordered frames plus a versioned source manifest), which is more specific than the name alone. It stops short of differentiating from siblings such as read_inspiration_bundle or read_inspiration_source, so an agent must infer which one surfaces the raw asset versus the source.

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 only conditional guidance is "Set includeImages to false for metadata only," which is a per-parameter hint rather than a when-to-use rule. There is no statement about when this tool is preferable to read_inspiration_bundle or read_inspiration_source, so usage is only implied by the described return type.

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