Used Fork Truck

screen_truck

Read-only

Screen a truck the way the sell page does. Starts from that class band in the autumn 2026 price book, adjusts for year, hours, grade, and whether the power is known, then returns a low, a point, and a high. A screen, not an appraisal and not a bid. Year on the form runs from 1998 to 2026. Grade is A, B, or C. Power is sound, unknown, or needs-work.

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>",
      "year": "<year>",
      "hours": "<hours>",
      "grade": "<grade>",
      "power": "<power>"
    },
    "name": "screen_truck"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Model year. The seller screen allows 1998 to 2026.
`grade`	Yes	A is cleared in writing. B is work ready. C names the defects and is priced as a project.
`hours`	Yes	Hours on the meter. The seller screen allows 0 or more.
`power`	Yes	sound means the battery or engine is known and sound. unknown means not tested. needs-work means it needs work.
`classId`	Yes	Price book class id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive operation. The description adds useful behavioral context: it starts from a class band in the autumn 2026 price book, adjusts for year, hours, grade, and power status, and returns a low, point, and high. It does not discuss error handling or edge cases, but it discloses the core methodology and output shape.

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?

The description is front-loaded with the core action and output, followed by scope clarifications. It is mostly efficient, though the final sentences restate year, grade, and power constraints that the schema already documents at 100% coverage.

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?

With no output schema and only read-only annotations, the description needs to explain both behavior and return values. It does so by stating the adjustment method and the low/point/high return shape, and it covers all required parameters through the schema plus relational context. A minor gap is that it does not explain how classId values relate to sibling price-band tools.

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 description coverage is 100%, so the schema already defines each parameter and its allowed values. The description adds relational meaning by explaining that classId selects the base price band and that year, hours, grade, and power are adjustment factors. It does repeat some schema details, but the adjustment model is genuinely useful semantic context.

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 uses a specific verb and resource: 'Screen a truck,' and explains that it returns a low, point, and high from a class-band baseline. It also distinguishes the tool from an appraisal and a bid, though it does not explicitly distinguish it from sibling tools such as get_price_band.

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 description provides implied usage by saying it is 'a screen, not an appraisal and not a bid,' which helps set the scope. However, it does not explicitly say when to use this tool versus get_price_band or list_price_bands, so the agent must infer the routing.

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?