Skip to main content
Glama

Share a price with the benchmark

share_price
Idempotent

Adds a price the user pays or was quoted, anonymously, to the benchmark of what buyers actually pay (a median is published once five reports exist for an item). The only tool here that stores anything. Call it ONLY after the user has explicitly agreed to share this price; never on your own initiative. Nothing identifying is stored: no account, no address. Do not put names of people or the user's company in supplier.

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": {
      "kind": "<kind>",
      "item": "<item>",
      "price": "<price>",
      "user_agreed": "<user_agreed>"
    },
    "name": "share_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
kindYes
termNogpu only; default ON_DEMAND
priceYestoken: input price in USD per 1M tokens; gpu: price per GPU-hour
contractNo
currencyNogpu only
supplierNoThe provider or channel the price is from, if the user said
user_agreedYestrue only if the user explicitly agreed to share this price
output_priceNotoken only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it is a non-destructive, idempotent write; the description goes well beyond that by disclosing anonymity guarantees ('no account, no address'), the publication threshold ('a median is published once five reports exist'), and the consent requirement. These are behavioral facts the agent could not infer from the structured fields.

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?

Four short sentences, front-loaded with what the tool does, then the consent gate, then the privacy constraint. No filler and no repetition of the schema.

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 9-parameter write tool with no output schema, the description covers the critical risks: consent, anonymity, and the publication threshold. It is silent on what a successful call returns or how duplicate reports are handled, though idempotentHint partially covers the latter.

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?

Schema coverage is 67% and already documents price units, term, currency, and supplier. The description adds real meaning on top: the privacy constraint on supplier and the consent semantics of user_agreed, which the schema only states mechanically. It does not clarify contract or output_price, so not a 5.

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?

States a specific verb and resource ('Adds a price ... to the benchmark') and explicitly positions itself against siblings with 'The only tool here that stores anything,' which immediately separates it from the read-only price tools.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('Call it ONLY after the user has explicitly agreed to share this price; never on your own initiative') plus a field-level exclusion ('Do not put names of people or the user's company in supplier'). This is exactly the when/when-not guidance an agent needs for a write tool.

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.