Skip to main content
Glama

Set list price

core_set_price
Destructive

Change an item's list price. Takes effect for documents raised from now on. Everything already raised keeps the price it was raised with — a quote accepted after this change still becomes an order at the quoted price (INV-19), and issued invoices never move. That is why this is a logged act and not a field edit: the moment the price changed is part of the record. Effects: item.unit_price changed for future documents only.

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": {
      "item_id": "<item_id>",
      "unit_price": "<unit_price>"
    },
    "name": "core_set_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesThe item. An existing item id.
unit_priceYesThe new list price per unit. In cents (integer minor units) — 1250 means $12.50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantial context beyond them: the change is forward-only, existing quotes and issued invoices are unaffected, and the act is logged for audit. It does not address permissions or whether the change can be reverted, which keeps it from a 5.

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?

The key effect is front-loaded in the first sentence, and the rest explains consequences efficiently. There is mild redundancy — 'Everything already raised keeps the price it was raised with' is restated by the quote and invoice examples — and the INV-19 reference is unexplained, but overall it is tight.

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 two-parameter mutation with no output schema, the description covers the essential semantics: scope of effect, retroactivity, and audit logging. It omits error behavior (e.g., invalid item id) and reversibility, which are minor gaps given the annotations and complete schema.

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 both item_id and unit_price (including the cents convention) are already fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Change an item's list price.' It is unambiguous and clearly distinct from sibling tools like core_create_item or core_set_credit_limit, which operate on different resources.

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

Usage Guidelines4/5

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

It gives clear context for when the effect applies ('documents raised from now on') and implicitly contrasts this with a plain field edit ('this is a logged act and not a field edit'). It does not name an alternative tool or state when not to use it, so it falls short of a 5.

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.