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

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

anchoredObject_getSettings

Retrieve anchor position, offset, and frame settings for a specific object and page in an InDesign document.

Instructions

Get anchored object settings

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>"
    },
    "name": "anchoredObject_getSettings"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/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, and it discloses almost nothing. 'Get' implies a read, but there is no statement of what settings are returned, whether the object must exist, whether settings include position/anchor properties, or any permission requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short, but it is under-specified rather than concise — it consumes the space without conveying any information beyond the tool name. Nothing meaningful is front-loaded because nothing meaningful is present.

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?

There is no output schema and no annotation coverage, so the description must explain what comes back and how to address the target. It leaves the required pageIndex/itemIndex addressing scheme unexplained and never says which settings are returned, making it inadequate for an agent to call or interpret this tool.

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 coverage is only 33%: document_id is well documented in the schema, but the two REQUIRED parameters pageIndex and itemIndex have no description in either the schema or the description. With low coverage, the description was required to compensate, and it adds zero parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Get anchored object settings'), so the agent knows it is a read of anchored-object settings. However, it is essentially the tool name re-expanded into sentence case, with no scope details (which anchored object, which settings) and nothing to distinguish it from anchoredObject_setProperties, anchoredObject_setPosition, or anchoredObject_release. It sits between a vague purpose and a tautology.

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 when-to-use guidance, no prerequisites, and no named alternatives. The sibling set contains several anchoredObject_* tools and the agent is given no criterion for choosing getSettings over 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