Skip to main content
Glama

get_price_band

Read-only

One class from the price book, by id. Same band, capacity, and hours note as the book page. Not an offer.

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": {
      "classId": "<classId>"
    },
    "name": "get_price_band"
  }
}

Input Schema

NameRequiredDescriptionDefault
classIdYesPrice book class id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds that the record carries the same band, capacity, and hours note as the book page, which tells the agent what content fidelity to expect. 'Not an offer' is a meaningful semantic boundary that annotations cannot express. No output schema exists, so a bit more on the shape of the returned fields would have helped.

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?

Three short fragments, roughly twenty words, with the identifying information front-loaded and each clause carrying distinct content (what it is, what it returns, what it is not). Nothing is repeated or padded.

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 one-parameter lookup with full enum coverage and read-only annotations, the description covers identity, return content, and one key exclusion. Only the absence of any detail on the returned structure keeps it from being fully self-sufficient.

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 coverage is 100% with a single required classId constrained to an 8-value enum and documented as 'Price book class id.' The description's 'by id' adds nothing beyond that, so the schema does all the work and 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?

States the specific resource (one class from the price book) and the lookup key (by id), which implicitly contrasts with the sibling list_price_bands that returns the whole book. 'Not an offer' rules out a nearby misreading. It stops short of a clean verb+resource phrasing, but an agent can tell what it returns.

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 implied rather than stated: 'one class ... by id' suggests it is the single-item counterpart to list_price_bands, and 'Not an offer' warns against confusing it with offer data. There is no explicit 'use this when X, use list_price_bands when Y' routing, so the agent must infer the split.

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