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

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

font_glyph_insert

Insert a special glyph at the cursor position in Adobe InDesign by providing the glyph ID and optional font name.

Instructions

Insert a special glyph at the cursor position

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": {
      "glyphId": "<glyphId>"
    },
    "name": "font_glyph_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
glyphIdYes
fontNameNo
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.4/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 burden. It implies a mutation at the cursor but says nothing about whether the operation is undoable, what happens if the target document lacks the font, whether an active insertion point is required, or any error behavior. Only the minimal 'inserts at cursor' trait is disclosed.

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 short, front-loaded sentence with zero filler. It is efficient, though its brevity reflects under-specification rather than disciplined concision.

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, and only 33% schema coverage, the description is too sparse. It omits the fontName/glyphId semantics, preconditions, and any behavioral consequences that an agent needs to call it 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 33% – only document_id is documented in the schema. The description mentions 'glyph' but does not clarify whether glyphId is a Unicode codepoint, a glyph index in the font, or something else, nor does it explain that fontName selects the source font. The two undocumented parameters receive no compensating detail.

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 names a specific verb (insert) and resource (a special glyph) plus the target location (cursor position), so the core action is understandable. However, it does not explain what distinguishes a 'special glyph' from normal text insertion, nor does it differentiate this tool from font-related siblings like font_find or font_change. Purpose is identifiable but thin.

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 versus alternatives such as text_setContent or text_applyFont, no prerequisites (e.g. a text frame must be active), and no mention of the cursor/selection requirement. The agent is left to infer all usage conditions.

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