Skip to main content
Glama

design_library_import

Idempotent

Save an upstream design reference to .design-references without overwriting the approved DESIGN.md, preserving design approvals while importing new references.

Instructions

Save an upstream design reference in .design-references without overwriting the approved DESIGN.md.

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": {
      "project_path": "<project_path>",
      "id": "<id>"
    },
    "name": "design_library_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent, open-world write, and the description adds meaningful context beyond them: writes land in the .design-references directory and the approved DESIGN.md is explicitly preserved. It still does not say what happens on a duplicate id or whether re-imports replace existing reference files.

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?

A single front-loaded sentence with the action, destination, and the key safety guarantee stated up front. Nothing superfluous, and the preservation constraint is placed where it will be read first.

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?

The behavioral side is well covered for a small two-parameter write with annotations, but with no output schema and zero parameter documentation, an agent still lacks enough to confidently supply both required values or predict the result of the save.

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?

Both parameters (project_path, id) are required and schema description coverage is 0%, so the description must carry the meaning. It does not explain what 'id' identifies (artifact name, upstream source key) or the expected form of project_path, leaving the caller to guess the two values the tool cannot run without.

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 ('save') and resource ('upstream design reference') plus the destination directory '.design-references'. It implicitly contrasts with reading/cataloging siblings by framing the action as capturing an upstream reference, but it never names an alternative tool explicitly.

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?

Usage is implied: use this when you need to persist an upstream reference while preserving the approved DESIGN.md. There is no explicit statement of when to use this versus design_library_read, design_library_catalog, or design_library_guidance, and no prerequisites are given.

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