Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

search_vault

Read-onlyIdempotent

Find implementation-ready UI snippets and interaction studies by task, category, pack, or platform for reuse in design and coding work.

Instructions

Find implementation-ready snippets and interaction studies by task, category, pack and platform.

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

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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds no behavioral context beyond that: nothing about result ordering, pagination behavior, or what happens when filters are combined or omitted. For a search tool with limit/offset and a 500-item excludeIds cap, this is a notable gap.

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?

It is a single front-loaded sentence with no filler, which is efficient. Its brevity borders on under-specification given nine parameters, but nothing in the sentence itself is wasted or redundant.

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 tool is complex — nine optional parameters, a nested projectBrief object, an enum, and no output schema — yet the description is one clause long. An agent would not know how projectBrief or projectContext influence ranking, how limit/offset interact, or what a result looks like, so the definition is incomplete for this complexity.

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%, so the description carries the full burden, yet it only gestures at 'task, category, pack and platform' — loosely mapping to category, packId, platform, and possibly query. The most semantically opaque inputs (excludeIds, projectBrief with businessType/sectionPurpose/relatedIndustries, projectContext, limit/offset) are left entirely unexplained in both schema and description.

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 gives a specific verb ('Find') and names the resources returned ('implementation-ready snippets and interaction studies'), which tells an agent what kind of content lives in the vault. It also lists the searchable dimensions (task, category, pack, platform), distinguishing it as a search tool rather than a getter like get_vault_resource. It does not explicitly contrast itself with content-search siblings such as search_inspirations or search_icons, so it stops short of a 5.

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?

Usage is only implied by the phrase 'by task, category, pack and platform' — there is no statement of when to search versus fetch a specific resource, and no mention of alternatives or prerequisites. With nine sibling tools including retrieval-oriented ones (get_vault_resource, get_design_pack), an agent gets no routing guidance.

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