Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

get_design_spec

Retrieve the DESIGN.md specification for a selected Figma frame, including YAML tokens, light/dark themes, components, and a WCAG 2.2 accessibility audit.

Instructions

Get the DESIGN.md specification (YAML tokens, Multi-Theme Light/Dark modes, Components, and WCAG 2.2 Accessibility Audit) for the selected Figma frame.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the shape of the returned artifact (YAML tokens, dual themes, components, accessibility audit), which is genuinely useful context. It omits whether the call is read-only, what happens if no frame is selected, and any size/performance characteristics of returning a full spec.

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?

A single front-loaded sentence with no filler, and the resource is named before the payload contents. The parenthetical list is dense but each item earns its place by telling the agent what the document contains.

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?

With zero parameters and no output schema, the description must carry the return-value burden, and it does so at a high level by listing the spec's sections. It falls short on prerequisites (must a frame be selected first?) and on how this aggregate result relates to the more granular sibling tools.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The mention of 'the selected Figma frame' usefully clarifies that input is implicit ambient state rather than a parameter.

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 ('Get') and resource ('DESIGN.md specification') and enumerates the payload: YAML tokens, Light/Dark themes, components, and a WCAG 2.2 audit. However, it does not differentiate itself from siblings like get_design_tokens or get_accessibility_report, whose names suggest overlapping content.

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?

There is no guidance on when to choose this aggregate spec tool versus the narrower get_design_tokens or get_accessibility_report. The phrase 'for the selected Figma frame' implies a selection prerequisite, but that condition is never stated as a requirement or contrasted with alternatives.

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