Skip to main content
Glama

Say what a supplier sells

purchasing_save_supplier_items

Which Inventory items a supplier sells: their article code, the unit cost in the supplier's currency, the pack size and minimum order, the lead time in days, and a fixed quantity to order at a time when there is one. Saved by SKU (saving again changes it). The first supplier of an item is its preferred one; preferred: true moves it. purchasing_draft_reorders orders from the preferred supplier. Costs $0.005 per item saved; nothing if none are found.

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": {
      "supplier": "<supplier>",
      "items": "<items>"
    },
    "name": "purchasing_save_supplier_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
supplierYesA supplier_id, or the supplier's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag this as a non-destructive write, and the description adds useful behavior: upsert-by-SKU, preferred-supplier movement, and per-item billing cost. It stops short of explaining auth needs, replacement/merge semantics, or the response shape.

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?

The description is dense, front-loaded with the core data model, and every sentence carries information: saving semantics, preference behavior, downstream ordering, and cost.

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 nested supplier-item save operation, it covers the important fields and downstream effect well enough, especially since annotations cover safety. The main gap is that it does not say whether re-saving partially updates or replaces an existing supplier-item record.

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

Parameters4/5

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

With 50% schema description coverage, the description compensates by explaining supplier article code, unit cost in supplier currency, pack size, minimum order, lead time, and fixed order quantity. It adds meaning but does not clarify all nested-field semantics, such as whether omitted fields are cleared or retained.

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 names the specific resource, supplier-item links, and enumerates the data being saved, with 'Saved by SKU' implying an upsert. It is clear what the tool does, though it does not explicitly contrast itself with the sibling list or supplier-save tools.

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?

Usage is implied through 'saving again changes it', the preferred-supplier rule, and the note that purchasing_draft_reorders uses preferred suppliers. However, it does not explicitly say when to use this tool versus purchasing_list_supplier_items or purchasing_save_supplier.

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