Skip to main content
Glama

Record the mapping answer

prepress_confirm
Destructive

Record the customer's approval of a PROPOSED mapping. The mapping carries an APPROVE_MAPPING confirmation in pending_confirmations, and answering it here with the approve option is what unlocks prepress_submit_mapping.

confirmation_id and option_id must both be copied verbatim from the confirmation — option_id is the listed option, never a phrase the customer typed and never a value you compose. If the customer does not want this mapping, do not answer the confirmation: call prepress_map_pages with the positions they ask for, or ask for corrected files.

Returns a job_id. The result is the same shape as prepress_map_pages. Job errors: ConfirmationNotFoundError (already answered, or wrong id), InvalidAnswerError (option not on that confirmation), AlreadyMappedError (this item already went through the one-way door), or ItemHasDesignError (the item holds an attached design, which is what prints).

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": {
      "session_id": "<session_id>",
      "order_id": "<order_id>",
      "item_id": "<item_id>",
      "confirmation_id": "<confirmation_id>",
      "option_id": "<option_id>"
    },
    "name": "prepress_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
order_idYes
option_idYes
session_idYes
confirmation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the downstream unlock of prepress_submit_mapping, the one-way-door nature of the mapping, the identical result shape to prepress_map_pages, and four named job errors including AlreadyMappedError. What it does not state is that answering is final for this item in plain terms rather than only via an error name, but the destructive semantics are effectively reinforced.

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 primary action and its unlock effect are front-loaded, and the rejection path, parameter rules, and error list follow in a logical order with no filler paragraphs. The doubled phrasing around option_id ('never a phrase the customer typed and never a value you compose') is emphatic but slightly redundant.

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

Completeness4/5

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

For a destructive mutation with five opaque parameters, the definition covers the decision logic, the verbatim-id rule, the downstream effect, and the failure modes, and an output schema exists so return values need not be spelled out. The remaining shortfall is the unexplained identity parameters (session_id, order_id, item_id), which is the only thing an agent could still get wrong.

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 0%, so the description must carry the burden, and it only explains two of five parameters: confirmation_id and option_id must be copied verbatim, with option_id restricted to a listed option and never a composed phrase. session_id, order_id, and item_id get no semantics at all, leaving a significant gap for a fully required five-parameter call.

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

Purpose5/5

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

The opening sentence names a specific verb and resource (record the customer's approval of a PROPOSED mapping) and ties it to the APPROVE_MAPPING confirmation, so the action is unambiguous. It also distinguishes itself from siblings by naming prepress_submit_mapping as the thing it unlocks and prepress_map_pages as the alternative path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use trigger (the mapping carries an APPROVE_MAPPING confirmation in pending_confirmations) and an explicit when-not-to-use branch: if the customer rejects the mapping, do not answer the confirmation, call prepress_map_pages with positions instead or ask for corrected files. Alternative tools are named with the condition that selects them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources