Skip to main content
Glama

Who am I

figma_local_whoami
Read-only

Returns the authenticated Figma user, auth method, tool prefix, and plugin bridge status. Use it to diagnose file access or permission errors, rate limits, and plugin detection failures.

Instructions

Returns the authenticated Figma user (handle, email, id), how this server authenticates, the tool name prefix, and the status of the companion plugin bridge (which files have the plugin open, their current page and selection). Use this tool when you hit file access or permission errors, rate limits, or when figma_local_use_figma cannot find the plugin.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them by disclosing that this is a self-diagnostic that reports auth method and live plugin-bridge state (open files, page, selection). It does not say what happens when unauthenticated or when the plugin is absent, which is the main remaining behavioral gap for a diagnostic tool.

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, no filler. The payload is front-loaded in sentence one and the routing guidance in sentence two, so an agent can stop reading after either depending on its need.

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?

With no output schema, the description carries the return-value burden and does so by naming the four result categories and the nested bridge details. It is nearly complete for a diagnostic probe, lacking only failure/unauthenticated behavior and any hint about the response shape.

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 for a no-parameter tool applies. The description correctly implies no inputs are needed by framing it as a pure status probe.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and enumerates exactly what is returned: the authenticated user (handle, email, id), the server's auth method, the tool name prefix, and the companion plugin bridge status including open files, current page and selection. That level of specificity distinguishes it from every sibling, which are all content-fetching tools rather than diagnostics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete trigger conditions — file access or permission errors, rate limits, or figma_local_use_figma failing to find the plugin — and explicitly names the sibling whose failure routes here. It stops short of stating when not to call it (e.g. as a routine first step), so it is clear but not fully exclusionary.

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