Skip to main content
Glama
Sign In
indesign-nutria-mcp

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shape_create

Create geometric shapes—rectangles, ellipses, polygons, or lines—on an InDesign page by giving bounds, fill and stroke colors, and a page index.

Instructions

Create a geometric shape (rectangle, ellipse, polygon, line)

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": {
      "pageIndex": "<pageIndex>",
      "type": "<type>",
      "bounds": "<bounds>"
    },
    "name": "shape_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
boundsYes
fillColorNo
pageIndexYes
layerIndexNo
document_idNoWhich open document to act on: a name (see document_listOpen) or a 0-based index. Defaults to the front document.
strokeColorNo
strokeWeightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing beyond the basic action. It does not state the coordinate space for bounds, how pageIndex/layerIndex default, whether the shape is placed on the current layer, what permissions are needed, or what happens on failure for a mutation tool.

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?

It is a single front-loaded sentence with no redundant phrasing or filler. The terseness is efficient, though it is arguably under-specified rather than tightly scoped.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, a nested bounds object, and 8 mostly undocumented parameters, a one-line description is inadequate. An agent lacks the coordinate conventions, defaults, and placement behavior needed to call this correctly.

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?

Schema description coverage is only 13% (essentially just document_id), leaving 7 of 8 parameters undocumented. The description only echoes the type enum values and adds no meaning for bounds, pageIndex, layerIndex, fillColor, strokeColor, or strokeWeight, so it fails to compensate for the schema gap.

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 states a clear verb and resource ('Create a geometric shape') and enumerates the four supported shape types, which matches the type enum. However, it offers no differentiation from the closely related siblings shape_rectangle_create, shape_ellipse_create, shape_polygon_create, and shape_line_create, so an agent cannot tell from the description alone when to prefer this generic tool over the specialized ones.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The presence of four type-specific sibling creation tools makes this omission significant, since the description gives no cue about how this generic tool relates to them.

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