Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

get_vault_resource

Read-onlyIdempotent

Retrieve source code, implementation prompts, documentation, or extras for a Vault ID by Atlas ID, slug, Remix text, or gallery URL. Use it to pull verified HTML/CSS references.

Instructions

Get source and an implementation prompt, supporting documentation, or extras for a Vault ID.

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

Input Schema

NameRequiredDescriptionDefault
idNoAtlas ID, slug, copied Remix text, or gallery URL.
slugNo
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.5/5.0
Behavior2/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 safety is covered. Beyond that, the description only hints that returned content varies by kind (implementation prompt vs documentation vs extras); it says nothing about size, structure, pagination, or what happens when the id is ambiguous or unresolvable, and there is no output schema to lean on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, so length is fine, but the sentence is grammatically tangled ("Get source and an implementation prompt... for a Vault ID") and buries the one actionable detail — the three content kinds — behind awkward wording.

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?

With no output schema, no required parameters, a 3-parameter schema at 33% coverage, and a `content` enum that changes what is returned, the description should explain the resolution behavior and the content modes. It gestures at the modes but leaves `slug` vs `id` and the return shape entirely unexplained.

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 coverage is 33%: only `id` is documented ("Atlas ID, slug, copied Remix text, or gallery URL"), while `slug` and `content` are bare. The description partly compensates by enumerating the three content kinds ("implementation prompt, supporting documentation, or extras"), which maps onto the `content` enum, but it never explains how `slug` relates to `id` or which to supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ("Get") and a resource set ("source and an implementation prompt, supporting documentation, or extras for a Vault ID"), so the general shape is inferable. However, the phrasing is muddled — "Get source and an implementation prompt" reads as two objects joined by a conjunction — and it never states what a "Vault ID" resolves to or how this differs from siblings like get_design_pack or get_reference_guide.

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 guidance, no prerequisites, no mention of alternatives. The agent must guess whether to reach for this tool or search_vault/get_design_pack based purely on the names of siblings, which the definition never addresses.

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