Skip to main content
Glama

enrich_catalog

Submit product catalog data to generate a quote, or confirm a previously displayed quote with batch_id and acceptance.

Instructions

Submit a catalog for a quote with body. Accept a previously displayed quote with batch_id, acceptance and confirm=true.

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": "enrich_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
confirmNo
batch_idNo
run_labelNo
acceptanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and largely drops it. It never says whether submitting a catalog consumes credits or creates a billable quote, what `confirm=true` protects against, whether the submit and accept paths have different side effects, or how long a quote/batch_id stays valid — all critical given the sibling tools retry_payment and get_usage.

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

Conciseness3/5

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

Two short sentences, front-loaded, with nothing extraneous. However the phrasing 'with body' is elliptical and the second sentence packs the acceptance contract into a comma list without structure, so the brevity comes partly from under-specification.

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 tool with a deeply nested 500-record schema, five parameters, no annotations and no output schema, the description is far too thin. It omits the required body structure, the meaning of run_label, what is returned (presumably a quote plus batch_id), and any cost or confirmation semantics.

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 0% across 5 parameters including a large nested `body` object with required `workflow`, `records` and `parameters`. The description only names four of the five parameters and never mentions `run_label`, the fixed `catalog_local_v1` workflow value, or what a record minimally needs; its one contribution is pairing batch_id/acceptance/confirm as the acceptance mode.

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 concrete verb and resource ('Submit a catalog for a quote') and also names a second mode ('Accept a previously displayed quote'), so an agent can grasp the two-step submit-then-accept flow. It does not reconcile the name 'enrich_catalog' with the described submit-for-quote behavior, nor differentiate from siblings like estimate_cost, but the core action is clear.

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

Usage Guidelines3/5

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

It gives real mode-selection guidance: use `body` to submit a fresh catalog, or `batch_id`, `acceptance` and `confirm=true` to accept a previously displayed quote. That is useful triggering context, but there is no when-not guidance, no prerequisites (credits, prior call to estimate_cost), and no explicit routing away from siblings.

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