Skip to main content
Glama

design_library_read

Read-onlyIdempotent

Retrieve the complete version-pinned upstream DESIGN.md for a catalog ID so you can review exact design references without version drift.

Instructions

Read a full version-pinned upstream DESIGN.md by catalog ID.

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

Input Schema

NameRequiredDescriptionDefault
idYes
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds one piece of real context — that the document is version-pinned and fetched from upstream — but it does not explain what 'refresh' does behaviorally (cache bypass? re-fetch?) or what the caller receives.

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; the distinguishing qualifiers come before the lookup key. It is efficient, though the density of 'version-pinned upstream' would benefit from a short clarifying clause.

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 two-parameter read tool with no output schema, the definition covers the core action but leaves the second parameter's behavior and the returned content shape unaddressed. An agent could call it, but not confidently predict what refresh changes.

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% across 2 parameters, so the description carries the full burden. It maps 'catalog ID' to the id parameter but says nothing about 'refresh', whose default false and cache-refresh semantics are left entirely to guesswork.

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 and resource: 'Read a full version-pinned upstream DESIGN.md by catalog ID.' The qualifiers 'version-pinned' and 'upstream' distinguish it from a local read or a catalog listing, though it never names design_read or design_library_catalog explicitly as the alternatives.

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?

'by catalog ID' implies the prerequisite that a catalog entry must exist, and the sibling names suggest design_library_catalog is the discovery step. However, there is no explicit when-to-use or when-not-to-use guidance, and nothing says when to prefer this over design_read.

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