Skip to main content
Glama

enrich_title

Turns a product title into structured product data—type, attributes, categories, buyer keywords, and market research—with a preview by default and optional confirmation before submitting.

Instructions

Preview by default. Set confirm to request approval for this exact body.

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": {
      "body": "<body>"
    },
    "name": "enrich_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
confirmNo
run_labelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: the default is a non-committing preview and confirm triggers an approval step for the exact submitted body. That is valuable safety context. It says nothing, however, about whether the call is billable, what the preview returns, or what side effects approval produces.

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?

Two tight sentences with no filler, and the default (preview) is front-loaded ahead of the opt-in (confirm). Brevity is not the problem here; the issue is that so little is said rather than too much.

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, entirely undocumented body schema, no annotations, and no output schema, the description covers only the confirm flag's semantics. An agent still cannot tell what enrichment produces, what the required parameters array means, or what a preview returns, which is a substantial gap for a tool of this complexity.

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% and the body object nests roughly ten properties (title, locale, market, channel, keywords, language, attributes, parameters, description, client_product_id), none of which are explained anywhere. The description clarifies confirm's meaning and gestures at body being submitted verbatim, but leaves run_label and every nested field undocumented.

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

Purpose2/5

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

The description never states what the tool does: no verb, no resource, no statement of what 'enrich' means or what a title gets enriched with. It only describes the preview/confirm lifecycle, leaving the actual purpose to be inferred from the name alone. It also does nothing to distinguish this from siblings like enrich_catalog or generate_content.

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 a usable rule for confirm ('set confirm to request approval for this exact body'), which implies a preview-then-commit workflow. But there is no guidance on when to choose enrich_title over enrich_catalog, generate_content, or research_market, and no prerequisites or cost implications are mentioned.

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