Skip to main content
Glama

figma_status

Checks whether the Figma plugin is connected and reports the currently open file and page, returning a status even when no plugin is connected.

Instructions

查询插件是否已连接,以及当前文件与页面。未连接也成功返回。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one meaningful trait: it returns success even when the plugin is not connected, so callers must inspect the payload rather than rely on errors. It does not explain what 'connected' means, timeouts, or the shape of the return value.

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, front-loaded with the purpose and followed by the key non-error behavior. No filler, though the second sentence could be slightly more explicit about what 'returns successfully' yields.

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 zero-parameter status probe with no output schema, the description names the three pieces of information returned (connection state, file, page) and warns about the always-success behavior. Return formatting details are the only real gap.

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 no parameters, so the baseline is 4; there is nothing for the description to clarify beyond confirming it is parameterless.

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?

States a specific query: whether the plugin is connected, plus current file and page. An agent can tell it is a status/probe tool rather than one of the figma_get_* readers, though the overlap with figma_get_current_page is not addressed.

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?

Use is implied (call it to check connection before other operations), but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as figma_get_current_page or figma_get_document_info.

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