Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

read_inspiration_source

Read-onlyIdempotent

Read numbered source lines from a Design Atlas inspiration entry by ID, slug, gallery URL, or Remix text. Use offset and line range paging to pull verified HTML/CSS when remixing a reference.

Instructions

Read numbered source lines. Continue with nextOffset in the current range, then nextStartLine at offset zero.

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

Input Schema

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

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add genuinely new behavioral content — that results are numbered lines and how to page forward — but it names continuation fields (nextOffset, nextStartLine) that appear nowhere in the schema or an output schema, leaving the agent to discover them at runtime.

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 terse sentences, no filler, and the continuation instruction is front-loaded after the core action. The brevity is efficient, though it verges on under-specification rather than crispness.

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 8 parameters at 13% coverage and no output schema, the definition should explain the identifier options and the two competing paging mechanisms. Instead it explains only continuation, and using field names the agent cannot verify, so a correct call is not fully derivable from the definition.

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 13% across 8 parameters, so the description must carry the burden and does not. It gestures at offset and startLine through continuation tokens, but says nothing about id, path, slug, version, limit, or lineCount, nor the difference between offset/limit and startLine/lineCount ranges.

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?

"Read numbered source lines" gives a verb and a rough object, but never says what a "source" is (an inspiration's instructions file? a gallery listing?) or what unit is being read. It does not distinguish this from siblings such as read_inspiration_bundle or get_inspiration, so an agent must guess which read tool applies.

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?

The only guidance is a pagination recipe for continuing a read already in progress; there is no statement of when to choose this tool over the other read/search siblings, nor any exclusion. Implied usage exists but tool selection is unaddressed.

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