Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

read_inspiration_bundle

Read-onlyIdempotent

Read a specific versioned file from a design inspiration bundle using text offsets or verified base64 chunk transfer.

Instructions

Read a versioned file. Text offsets count Unicode code points. In transfer mode, concatenate decoded base64 byte chunks and verify the complete SHA-256.

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": "read_inspiration_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAtlas ID, slug, copied Remix text, or gallery URL.
modeNo
pathNoinstructions.md
slugNo
limitNo
offsetNo
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world safety, so the description's job is to add protocol detail, and it does: offsets are counted in Unicode code points, transfer mode returns base64 chunks that must be concatenated, and the complete SHA-256 should be verified. These are non-obvious operational facts an agent would otherwise get wrong. It omits what happens at offset/limit boundaries and whether verification failure is an error response.

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?

Three short sentences, no filler, with the core action front-loaded before the two protocol caveats. The only weakness is that the opening sentence's generic wording ('a versioned file') spends a sentence without anchoring the tool to its actual resource.

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 read-only, non-destructive tool with no output schema, the description does the essential protocol work (chunk concatenation, hash verification, offset units). But with seven mostly undocumented parameters, no output schema, and no explanation of id/slug/path precedence or pagination via limit, an agent cannot reliably construct a correct call from this definition alone.

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 only 14%, so the description carries most of the burden, yet it clarifies only two of seven parameters: offset (code points) and mode (transfer). The most consequential parameters — id (which is the only one with a description), slug, path (with a default), limit and version — get no explanation of format, precedence, or interaction.

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 description states a concrete verb and resource ('Read a versioned file'), but never uses the domain term 'inspiration bundle' and gives no basis for choosing between this and siblings such as read_inspiration_source. An agent knows it reads a file but not which file family or resource this covers.

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 statement of when to use this tool, when not to, or which alternative applies for plain text vs. transfer access. The mention of 'transfer mode' hints at a mode choice but doesn't explain when an agent should pick one mode over the other.

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