Loading ToolBench
Model Context Protocol server for Figma integration
Single tool 'get_figma_data' has a reasonable name and basic schema, but critical gaps undermine quality. Description is adequate (56 chars) but lacks WHEN to use it and prerequisites. Input schema is present with Zod types (fileKey required, nodeId/depth optional) but parameter descriptions are minimal (10-20 chars each). Output is returned as YAML text without documented schema structure, LLMs cannot plan downstream calls or extract typed fields. No error handling guidance; catch-all error response provides no recovery path. Tool lacks idempotency documentation and does not indicate whether it's read-only (though risk is marked READ_ONLY). Missing output schema documentation is a critical gap per pattern:tool.
Fetch layout info from a Figma file
Output schema not documented. Tool returns YAML-formatted text without specifying structure of 'metadata', 'nodes', 'globalVars' fields. LLMs cannot extract typed data or plan chained calls.
Parameter descriptions are too brief (10-20 chars). 'Optional node ID to fetch specific node' and 'Optional depth parameter for nested node retrieval' lack format/range guidance. LLMs cannot infer valid values.
Error handling provides no recovery guidance. Catch-all 'Error fetching file: {error}' response gives LLM no actionable next step. Should categorize as retryable vs user-fixable and suggest alternatives.
Tool description lacks WHEN to use it and prerequisites. Does not explain when to call with nodeId vs without, or what depth values are valid. Missing dependency hints.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | <=2025-11-25 | v2 |
No idempotency guarantee documented. Tool fetches data but does not state whether repeated calls with same input return identical results, critical for agent retry logic.