Used Fork Truck

list_price_bands

Read-only

List the autumn 2026 used forklift price bands from the price book. Observed US independent listing ranges. Not inventory and not offers. Optional fuel filter: LP, Electric, Diesel, or Mixed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_price_bands"
  }
}

Input Schema

Name	Required	Description	Default
`fuel`	No	Optional fuel filter, the same filters as the price book.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered; the description adds the useful provenance that these are observed US independent listing ranges from a price book, i.e. data not commitments. Return shape and whether results are exhaustive are not stated.

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 the resource and scope, each carrying distinct information (period, provenance, exclusions, filter). Nothing is redundant with itself.

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 read-only list tool with a fully documented enum and annotations covering safety, this is nearly sufficient. The only gap is that no output schema exists and the description never hints at the fields a price band contains.

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% and the enum already lists LP, Electric, Diesel, Mixed with a note that these mirror the price book filters. The description merely restates those values, adding no new semantics; baseline 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?

States a specific verb (List) and a tightly scoped resource (autumn 2026 used forklift price bands from the price book). The clarifying clause 'Not inventory and not offers' and the sibling 'get_price_band' (single-band lookup) make the listing-vs-single distinction legible without opening a schema.

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?

'Not inventory and not offers' gives explicit negative scope, telling the agent when this tool is the wrong choice. It does not, however, route to a specific sibling such as get_price_band for a single band, so the alternative is only implied.

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

All Used Fork Truck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?