Skip to main content
Glama

add-product

Creates a new catalog product using an ID, name, price, quantity, and description to support inventory and product management.

Instructions

Add a new product to the catalog

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": {
      "id": "<id>",
      "name": "<name>",
      "price": "<price>",
      "quantity": "<quantity>",
      "description": "<description>"
    },
    "name": "add-product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier for the product
nameYesThe name of the product
priceYesUnit price of the product
quantityYesInitial stock quantity
descriptionYesBrief description of the product

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden, and it discloses very little. It does not say whether creation fails on a duplicate id, whether the write is reversible, whether any authorization is required, or what the response contains after a successful add — all critical for an irreversible mutation with five required fields.

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 eight-word sentence with no filler and the action front-loaded. It is efficient, though the terseness is partly what leaves usage and behavioral gaps unaddressed.

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 five-required-parameter mutation tool with no annotations and no output schema, the definition is too thin. The schema covers field names, but conflict handling, side effects, and return behavior are left entirely undocumented.

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 every one of the five required parameters is individually documented in the schema. The description adds no extra meaning such as id uniqueness constraints, price/quantity domain rules, or format expectations, so it stays at the baseline.

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 specific verb and resource ('Add a new product') plus the destination ('to the catalog'), so an agent immediately knows this is a create operation on products. It does not name or contrast with any sibling, but the siblings listed (get-product-by-id, get-products, get-alerts, get-forecast) are all reads, so the write/read distinction is implicit rather than explained.

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 tool versus alternatives, no prerequisites, and no exclusions. The agent is not told what to do if the product already exists or whether a separate update tool should be used for existing catalog entries.

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