Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

search_inspirations

Read-onlyIdempotent

Find authored design reference studies by query, platform, category, or project context, then review candidates with source links and inspect a selected ID.

Instructions

Find authored reference studies. Present the returned candidates with source links, then inspect the selected ID. Continue with nextSearchArguments.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
packIdNo
categoryNo
platformNo
excludeIdsNo
projectBriefNo
projectContextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that the operation is read-only, idempotent, and nondestructive. The description adds candidate presentation with source links and a continuation mechanism, but does not explain result ordering, empty-query behavior, or how continuation relates to limit and offset.

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?

Three short sentences front-load the purpose and then cover result handling and continuation without filler. Some wording is telegraphic, but the resulting ambiguity is a completeness issue rather than unnecessary length.

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?

The high-level workflow is useful, but a nine-parameter tool with nested objects, no parameter documentation, and no output schema needs more guidance for reliable invocation. It leaves every search, filter, and pagination input unexplained and only sketches the inspection and continuation handoffs.

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

Parameters1/5

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

With 0% schema description coverage across nine parameters, the description needed to compensate but explains none of query, limit, offset, packId, category, platform, excludeIds, projectBrief, or projectContext. The selected ID and nextSearchArguments refer to subsequent workflow steps rather than documenting these inputs.

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?

“Find authored reference studies” supplies a specific verb and resource while clarifying what an inspiration represents. It does not explicitly distinguish this search from sibling inspection or retrieval tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a concrete workflow: present candidates with source links, inspect the selected ID, and continue using nextSearchArguments. It does not provide exclusions or name the tool to use for inspection, so routing between alternatives remains incomplete.

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