Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_whoami

Identifies the current Figma user, open file, pages, and viewport, and reports which connected file was actually read when several files are available.

Instructions

Current Figma user, open file (name/key/editor type), pages and viewport. With several files connected, pass fileKey — its reply names the file it actually read.

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": "figma_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only status report and says the reply names the file actually read, but it never explicitly states read-only safety, permissions, side effects, or the full response shape.

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 no filler. The first sentence is a noun-phrase inventory rather than a proper sentence, but the content is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity one-parameter tool, the description lists the returned context and explains fileKey disambiguation. It remains somewhat incomplete because it lacks usage guidance and explicit read-only confirmation, with no annotations or output schema to fill those 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%, and the schema already documents fileKey's purpose and multi-file requirement. The description repeats that condition rather than adding format details or edge-case meaning beyond the schema.

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 enumerates the context it retrieves — current user, open file details (name/key/editor type), pages, and viewport — so the resource is clear, but it omits an explicit verb and does not distinguish it from sibling inspection/context tools.

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?

The only condition given is passing fileKey when multiple files are connected. There is no guidance on when to choose this tool over siblings such as figma_get_metadata, figma_inspect, or figma_get_selection.

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