Skip to main content
Glama

design_library_guidance

Read-onlyIdempotent

Generate a project-aware design implementation plan by combining design references with a current project audit. It provides actionable guidance without editing source files.

Instructions

Produce a project-aware design implementation plan using the full reference and current project audit. No source edits.

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

Input Schema

NameRequiredDescriptionDefault
idYes
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered; the description's 'No source edits' merely reinforces this. It adds some value by naming the inputs (full reference, current project audit), but says nothing about the shape of the produced plan or what happens when the audit is missing.

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?

Two short sentences with the core action front-loaded and the non-mutation caveat appended; nothing is wasted. It could be slightly sharper since the middle clause about reference and audit is vague.

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?

For a plan-generating tool with no output schema and fully undocumented parameters, the description is thin: it doesn't describe plan contents, input relationships, or failure conditions. Given the 2-param required schema at 0% coverage, more explanation is warranted.

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% across both parameters, so the description must carry the load. It only loosely conveys that 'project_path' is the current project; the required 'id' parameter is never explained at all (library id? profile id?), leaving an agent to guess.

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 uses a specific verb ('Produce') and a well-defined artifact ('project-aware design implementation plan'), which clearly distinguishes it from the read/catalog siblings in the design_library_* family. It falls short of a 5 because it doesn't explicitly name which sibling it replaces or how it differs from design_audit, leaving routing partly to inference.

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?

'using the full reference and current project audit' implies a prerequisite state (an audit must already exist) and hints at the intended workflow, but never states when to use this versus design_audit or design_library_read, nor any exclusions. The guidance is implied rather than explicit.

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