Skip to main content
Glama
the-real-talk

the-real-talk

create_ellipse

Creates an ellipse or circle in Figma with a set position, width, height, and optional parent frame.

Instructions

Create an ellipse (a circle if width = height).

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNo
widthNo
heightNo
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden, and it discloses almost nothing: no permission/auth requirements, no statement of what layer or page the node lands on, no coordinate-system semantics, and no confirmation that the operation mutates the document. Only the implicit mutation of 'create' is conveyed.

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?

A single front-loaded sentence with no filler. It is short because it is underspecified rather than because it is economical, but the phrasing itself is clean and immediately readable.

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

Completeness1/5

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

For a six-parameter document-mutating tool with no annotations and no output schema, this description leaves an agent unable to call it correctly: placement, defaults, and the identity of the created node are all unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Six parameters with 0% schema description coverage, yet the description only explains the width/height relationship. Nothing is said about x/y (absolute vs. relative, origin), name (auto-generated if omitted?), or parentId (defaults to current page?), leaving five of six parameters undefined in both places.

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 ('Create an ellipse'), which is enough to distinguish it from siblings like create_rectangle or create_frame. The parenthetical clarifies the circle special case but adds no scoping detail.

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?

No indication of when to use this versus create_rectangle, create_from_svg, or other shape creators, and no prerequisites or placement context given. The agent must infer everything from the name.

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

Deploy Server

Other Tools