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

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

transform_flip

Flip an InDesign object horizontally or vertically by specifying its page and item index to adjust orientation or mirror layouts.

Instructions

Flip an object horizontally or vertically

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>",
      "itemIndex": "<itemIndex>",
      "axis": "<axis>"
    },
    "name": "transform_flip"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisYes
itemIndexYes
pageIndexYes
document_idNoWhich open document to act on: a name (see document_listOpen) or a 0-based index. Defaults to the front document.

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?

No annotations are provided, so the description carries the full behavioral burden. 'Flip' implies a mutation, but there is no disclosure about whether the change is undoable, what permissions are required, what happens to locked objects, or the return value—only the axis behavior is stated.

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?

The single sentence is efficient, front-loaded, and has zero wasted words. It is appropriately sized for a concise statement, though it lacks the detail needed for a full definition.

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 four parameters, low schema description coverage, no annotations, and no output schema, the description is far too terse. It omits essential context an agent needs—what constitutes an 'object', how pageIndex/itemIndex identify it, and what side effects to expect.

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 25% (only document_id is documented), so the description should compensate for pageIndex, itemIndex, and axis. It merely restates the axis enum values ('horizontally or vertically') that are already in the schema, adding no meaning beyond what the schema provides.

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 ('Flip') and resource ('an object') with the axis options, so it is clear this is a geometric flip operation distinct from transform_rotate or transform_scale. However, 'an object' is vague and the description does not explicitly differentiate itself from siblings like transform_align or transform_rotate.

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?

The description offers no when-to-use guidance, prerequisites, or alternatives. It does not explain when flipping is appropriate versus rotating or scaling, leaving the agent to infer usage context entirely.

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