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

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

text_setDropCap

Apply drop cap formatting to a specified paragraph in an InDesign text frame by setting character count, line span, and character style for the opening letter.

Instructions

Set drop cap options for a paragraph

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>",
      "frameIndex": "<frameIndex>",
      "paragraphIndex": "<paragraphIndex>"
    },
    "name": "text_setDropCap"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
pageIndexYes
charactersNo
frameIndexYes
document_idNoWhich open document to act on: a name (see document_listOpen) or a 0-based index. Defaults to the front document.
characterStyleNo
paragraphIndexYes

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, and it discloses almost nothing: it doesn't say whether this mutates existing drop cap settings, what happens to unspecified options, whether the paragraph must exist or be selected, or what is returned. "Set" implies a write, but no safety, idempotency, or side-effect context is given.

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 or redundancy; it is efficiently sized. The brevity is partly a symptom of thin content, but as structure it is clean and readable.

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 7-parameter mutation tool with no annotations, no output schema, and only 14% schema coverage, the definition is inadequate. It omits targeting semantics, parameter meaning, and behavioral effects, leaving the agent without enough to call it confidently.

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 14% — just document_id is documented — leaving six parameters (lines, characters, characterStyle, pageIndex, frameIndex, paragraphIndex) undocumented in both schema and description. The description's mention of "drop cap options" loosely gestures at lines/characters/characterStyle but adds no formats, defaults, or range meaning.

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 specific verb ("Set") and resource ("drop cap options") with an explicit target ("for a paragraph"), which is enough to distinguish it from adjacent text_set* tools like text_setColumns or text_setKeepOptions. It is clear but does not explicitly contrast itself with any sibling, so it falls short of a 5.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no mention of the required pageIndex/frameIndex/paragraphIndex targeting workflow. The single sentence leaves the agent to infer everything about invocation context.

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