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

indesign-nutria-mcp

by nutriandrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

dataMerge_removeDataSource

Removes the active data merge source from an InDesign document, unlinking its fields so you can attach a different data file.

Instructions

Remove the current data source from the document

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataMerge_removeDataSource"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.1/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 burden. 'Remove' implies a mutation, but it doesn't disclose reversibility, whether merged records are affected, whether the link to the source file is severed, or what happens on a document with no data source.

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

Conciseness5/5

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

A single sentence with the verb and object front-loaded and zero filler. Every word earns its place.

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

Completeness3/5

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

For a simple one-parameter operation this is barely adequate: it names the action but omits the state the document must be in and the side effects of removal. Given no annotations and no output schema, a bit more behavioral context would complete it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single optional document_id parameter is fully documented in the schema (name or 0-based index, default front document). The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (remove) and resource (data source) plus the scope (from the document). An agent knows exactly what it does, but the description never distinguishes it from the sibling dataMerge_selectDataSource or explains the relationship, 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 when-to-use guidance, no prerequisite (e.g. a data source must already be selected via dataMerge_selectDataSource), and no note on what happens if none is set. Usage must be inferred entirely from the name.

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