Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

inspect_edition_source

Read-onlyIdempotent

Inventory images, headings, copy, buttons, and link destinations in supplied HTML before designing a page edition, with line/column evidence for each item.

Instructions

Inventory the actual images, headings, copy, buttons and destinations in caller-supplied HTML before designing a whole-page edition. Returns source line/column evidence. The server performs no network requests.

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": {
      "html": "<html>",
      "pageUrl": "<pageUrl>"
    },
    "name": "inspect_edition_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYes
pageUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the burden is light. The description still adds real value: it states the return payload includes source line/column evidence and that the server makes no network requests, which clarifies that only supplied HTML is touched and that results are traceable to source positions.

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, front-loaded with the inventory purpose followed by return shape and the no-network guarantee. Nothing is padded, though the phrase 'before designing a whole-page edition' is slightly oblique about the actual trigger.

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 only two required scalar parameters, no output schema and full annotation coverage, the description supplies most of what an agent needs. The one meaningful gap is the unexplained purpose of the required pageUrl parameter in a tool that performs no network access.

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 description coverage is 0%, so the description must compensate. 'Caller-supplied HTML' does clarify that the html parameter is markup content rather than a URL or identifier, but pageUrl is never explained — especially ambiguous given the explicit statement that no network requests occur.

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?

The description names a specific verb (inventory) and enumerates the exact resources extracted: images, headings, copy, buttons and destinations from caller-supplied HTML. It clearly reads as a pre-design inspection step rather than a design or retrieval tool, though it never explicitly contrasts itself with siblings like read_inspiration_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?

'before designing a whole-page edition' gives an implied trigger point in the workflow, which is genuine context. However, there is no when-not guidance and no named alternative for reading external or inspiration content, so the agent must infer the boundary itself.

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