Skip to main content
Glama

Suggest a price in soles

suggest_price
Read-onlyIdempotent

Calculates a starting listing price in Peruvian soles for a catalog product from USD market value, exchange rate, and condition discount, rounded to S/ 0.50.

Instructions

Suggest a listing price in Peruvian soles for a catalog product: USD market price x exchange rate x a condition discount, rounded to S/ 0.50. It is a starting point; the seller has the final word.

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": {
      "productId": "<productId>"
    },
    "name": "suggest_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
subTypeNoPrice sub-type, e.g. 'Holofoil'. Defaults to the first one with a price.
conditionNoCard condition: NM, LP, MP, HP or DMGNM
productIdYesproductId from search_cards

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes further by disclosing the underlying computation (USD market price x exchange rate x condition discount, rounded to S/ 0.50), which tells the agent the result is derived and deterministic. It does not cover failure behavior, e.g. what happens when no priced subType exists.

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 sentences, front-loaded with the core action and currency, with the formula embedded and the caveat placed last. Every clause carries information: verb, resource, currency, formula, rounding, and advisory framing.

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 three-parameter, read-only, idempotent tool with no output schema, the description supplies the essentials: what is computed, in what currency, and at what precision. The remaining gap is edge-case behavior when the product lacks price data, which an agent would need to interpret a failure or fallback.

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 the schema already documents productId, condition and subType, and the baseline is 3. The description adds only the notion that condition factors in as a 'discount' multiplier; it does not clarify how subType selection or condition grading shifts the result.

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 uses a specific verb and resource combination: 'Suggest a listing price in Peruvian soles for a catalog product.' It names the currency, the entity (catalog product) and even the output precision (rounded to S/ 0.50), which no sibling tool would match (create_draft, list_drafts, search_cards, search_help, search_store).

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 clause 'It is a starting point; the seller has the final word' communicates the advisory nature of the call and implicitly bounds when to use it, but there is no explicit when-to-use, no exclusions, and no reference to sibling tools such as search_cards (named only inside the schema, not the description). Usage is implied rather than stated.

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