Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

add_figma_annotation

Write AI feedback or review notes directly onto a selected Figma layer, attaching a native Dev Mode annotation and visual AI Note card for implementation context.

Instructions

Write an AI feedback note or annotation directly back onto the selected Figma layer (attaches native Dev Mode annotation + visual AI Note card on the Figma canvas).

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": {
      "annotation": "<annotation>"
    },
    "name": "add_figma_annotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
annotationYesFeedback, review note, or implementation status to attach to the Figma layer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose meaningful behavior beyond the name — that the call mutates the Figma file by attaching a native Dev Mode annotation and rendering a visible AI Note card on the canvas. It does not say whether an existing annotation is overwritten, what permissions or edit access are required, or whether the write is reversible.

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?

One front-loaded sentence with the action first and the side effects in a parenthetical; nothing is wasted. Minor redundancy in 'directly back onto' keeps it just short of ideal.

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?

For a one-parameter mutation tool with no output schema and no annotations, the description covers the what and where but omits success/failure behavior, overwrite semantics, and permission requirements. It is callable as written but leaves meaningful gaps for a write operation on user content.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that it holds 'feedback, review note, or implementation status.' The description restates the same idea ('AI feedback note or annotation') without adding format, length, or content-shape guidance, so the baseline of 3 applies.

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 gives a specific verb and resource: writing an annotation onto the selected Figma layer, and names the two artifacts produced (native Dev Mode annotation plus a visual AI Note card). That distinguishes it clearly from the read-oriented siblings (get_/list_/search_), though it never explicitly contrasts itself with them.

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 only implied: 'the selected Figma layer' signals that a layer must be selected first, and 'feedback note or annotation' hints at the review/feedback scenario. There is no explicit when-to-use, when-not-to-use, or named alternative for cases where you should not write back to the canvas.

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