Skip to main content
Glama
Sign In
Specky

Specky

by gbb-acelerators
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Figma to Spec

sdd_figma_to_spec
Read-onlyIdempotent

Extract design context from Figma and generate a requirements specification. Provides routing instructions for AI client to call Figma MCP's design context tool.

Instructions

Prepares a structured payload for extracting design context from a Figma file. The AI client should use the returned routing_instructions to call Figma MCP's get_design_context tool with the provided file key and node ID.

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": {
      "figma_file_key": "<figma_file_key>",
      "project_name": "<project_name>"
    },
    "name": "sdd_figma_to_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoOverwrite existing files if true
spec_dirNoSpec directory path (relative to workspace root).specs
project_nameYesKebab-case project name for the generated spec.
figma_node_idNoSpecific Figma node ID to extract. If omitted, extracts entire file.
figma_file_keyYesFigma file key extracted from the Figma URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0-rc.14

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds that it produces routing_instructions but does not elaborate on side effects or what the payload contains. With annotations present, the bar is lower, but the description could add context about file creation (given spec_dir and force parameters) which is absent.

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?

Two sentences: the first states the purpose, the second provides usage instructions. It is appropriately sized, front-loaded, and every sentence adds value. No redundancy.

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?

Given 5 parameters with full schema coverage and annotations, the description is somewhat complete but lacks explanation of the tool's output format and the fact that it likely generates files (given spec_dir and force parameters). No output schema exists, so the description should provide more behavioral context. Adequate but has gaps.

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 100% with each parameter having a description. The description does not add significant meaning beyond the schema; it mentions the concept of routing_instructions but doesn't tie into specific parameters. Baseline 3 is appropriate since the schema covers most details.

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 clearly states it prepares a structured payload for extracting design context from Figma, which is a specific verb+resource. It distinguishes itself from siblings by mentioning the production of routing_instructions for another tool, though it doesn't explicitly contrast with similar tools like sdd_figma_diagram.

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?

The description implies the tool is a preparatory step before calling Figma MCP's get_design_context, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. Context is provided but lacks exclusions or conditional logic.

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

Deploy Server

Other Tools