Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

list_design_packs

Read-onlyIdempotent

Lists visual design systems with their principles and linked pattern counts so coding agents can compare available packs before selecting references.

Instructions

List visual systems with their principles and number of linked patterns.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description does add useful content about what each item contains (principles and linked pattern counts), but says nothing about ordering, pagination, or whether the set is complete.

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?

One tight sentence that front-loads the action and resource and immediately qualifies the returned fields. Nothing is repeated and nothing is padding.

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 carries the return-shape burden and does so at a high level by naming the fields each entry exposes. The only gap is the absence of any pagination or volume hint for a list operation, which is a minor omission for a low-complexity, zero-parameter read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no semantic burden for the description to carry; schema coverage is 100% and the empty object schema is self-explanatory. Baseline 4 applies with no gaps to compensate for.

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 ('list') and resource ('visual systems', i.e. design packs), plus what each entry carries (principles, linked pattern count). It stops short of distinguishing itself from siblings such as get_design_pack or list_icon_packs, so an agent must infer that this is the enumeration entry point.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The list-vs-get relationship with get_design_pack is only inferable from the names, which the instructions say must not be assumed.

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