Skip to main content
Glama

My prices

my_prices
Read-onlyIdempotent

Your effective price (customer-group pricing applied) for public products, by 6-digit product code. Empty prices list = no group pricing on your account.

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": {
      "codes": "<codes>"
    },
    "name": "my_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding semantics annotations cannot express: prices are group-adjusted rather than list prices, coverage is limited to public products, and an empty price list specifically means no group pricing is configured. It stops short of describing response shape or behavior for codes that are not public/known.

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?

Two compact sentences with no filler, and the core meaning (effective, group-adjusted price) is front-loaded. The second sentence is terse to the point of being slightly telegraphic, but every sentence carries information.

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 simple read-only lookup with one parameter, good annotations, and no output schema, the description covers what is being fetched, what subset of products qualifies, and how to interpret an empty result. The main remaining gaps are the batch size limit and what a returned price entry contains, both minor for this tool's complexity.

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?

With a single parameter at 0% schema description coverage, the description must carry the load. It does clarify that input is a product code and that the expected format is 6 digits, but the schema pattern allows 4–10 digits and the description never mentions that the parameter is a batch array capped at 50 items, so it only partially compensates.

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 gives a specific resource and qualifier: the caller's *effective* price, with customer-group pricing applied, limited to public products, keyed by product code. That is far more precise than a restatement of the name. It does not explicitly contrast with any sibling, but no sibling in the list appears to return pricing, so ambiguity is low.

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 only implied: an agent can infer 'call this when you need prices for known product codes.' There is no explicit when-to-use statement, no statement about prerequisites (e.g. authentication/account scope beyond 'your'), and no mention of what to do for non-public products or unknown codes.

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