Skip to main content
Glama
Sign In

Edworking MCP

by io.github.Edworking
OverviewDiscussionsAdmin

Link a Figma frame

link_figma_frame

Link a selected Figma frame to an accessible task. Does not contact Figma. Use the plugin to add the reciprocal Dev Resource. Preserve requestId on retries.

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": {
      "requestId": "<requestId>",
      "taskId": "<taskId>",
      "url": "<url>"
    },
    "name": "link_figma_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS Figma design/file URL with node-id.
titleNoDoc title requested by the user.
taskIdYesExisting accessible task ID returned by list_tasks or search.
requestIdYesA unique UUID for this intended action. Reuse it unchanged when retrying the same action.

Output Schema

NameRequiredDescriptionDefault
linkYesEdworking record fields permitted for this connection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-open-world, non-destructive, non-idempotent operation, and the description adds real value on top: it discloses that no Figma API call happens and that requestId must be reused on retries to make the non-idempotent operation safe to repeat. It still omits what happens on a duplicate link, permission requirements, or failure modes.

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?

Four short sentences, front-loaded with the action and scope, then the non-network caveat, then the follow-up workflow, then the retry rule. No filler.

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?

An output schema exists, so return values need not be explained, and all four parameters are documented in the schema. The description covers the action, the offline behavior, the reciprocal step, and retry safety, leaving only error and permission behavior unaddressed.

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%, so every parameter already carries its own description, including the requestId retry rule. The description's 'Preserve requestId on retries' restates schema content rather than adding format or constraint detail, giving the baseline 3.

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 verb and resource ('Link a selected Figma frame to an accessible task') and rules out a misreading with 'Does not contact Figma.' It does not distinguish itself from the related sibling list_figma_tasks, so identity against siblings is only partly established.

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?

'Link a selected Figma frame to an accessible task' implies the precondition that the task already exists, and the plugin sentence implies a follow-up step for the reciprocal Dev Resource. There is no explicit when-not-to-use guidance or named alternative, so usage is implied rather than spelled out.

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

All Edworking MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources