Skip to main content
Glama

update_price

Destructive

Record a new current price on an item (manual correction; the old price is kept for comparison). Example: id, price=299.

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>",
      "price": "<price>"
    },
    "name": "update_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem ID
priceYesNew price
reasonNoWhy, for the change history
sourceNoai_check or manual

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The item ID"New value: +"Item ID"
    • changedInput schema / properties / price / description
      Previous value: -"New current price"New value: +"New price"
    • changedInput schema / properties / reason / description
      Previous value: -"Why this change was made (shown to user in change history)"New value: +"Why, for the change history"
    • changedInput schema / properties / source / description
      Previous value: -"Price update source"New value: +"ai_check or manual"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, and the description adds meaningful context beyond them: the old price is retained for comparison, which substantially softens the destructive read and tells the agent history is preserved. It still does not explain what the 'reason' field affects in the change history or whether setting the same price is a no-op.

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?

Two short sentences, front-loaded with the action and its key behavioral consequence (old price kept), followed by a compact usage example. No filler or redundancy.

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

Completeness3/5

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

For a four-parameter mutation tool with no output schema, the description covers the core action and the history-preservation behavior, but leaves open the role of the reason/source parameters and what the response contains. Adequate but not fully complete.

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%, so id, price, reason, and source are already documented structurally. The description only reinforces id and price with a terse example (id, price=299) and adds nothing about reason or source semantics, so the baseline 3 applies.

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 ('Record a new current price on an item') and clarifies the intent as a 'manual correction,' which separates it from a general update_item call. It does not explicitly name update_item as the alternative, so sibling differentiation is implied rather than stated.

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?

The parenthetical 'manual correction' signals when this is appropriate versus an automatic/imported price change, which loosely maps to the source enum. There is no explicit when-not-to-use guidance or mention of how this differs from update_item, so usage must be inferred.

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