Skip to main content
Glama

palletdimensions.com freight reference

List trailers and pallet ids

list_equipment
Read-onlyIdempotent

Lists the trailers and pallet ids that pallets_per_trailer accepts, with the inside dimensions it loads against.

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_equipment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the substantive behavioral detail that the result set includes inside dimensions the load is checked against, which goes beyond the annotations and beyond a bare parameter listing.

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?

A single front-loaded sentence with no filler. Every clause carries information: the listed resources, their consumer (pallets_per_trailer), and the extra dimension data.

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 zero-parameter, read-only reference lister with no output schema, the description covers what is returned and why it matters. It could be marginally stronger by stating the call order/relationship to pallets_per_trailer explicitly, but nothing essential is missing.

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?

The tool takes no parameters, so the baseline is 4; the description does not need to explain inputs. It instead spends its words describing the output content, which is the useful place to spend them here.

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 states a specific verb (Lists) and specific resources (trailers, pallet ids, inside dimensions), and ties its content to the sibling pallets_per_trailer by naming what that tool accepts. It is clear what the tool returns, though it doesn't explicitly frame itself as a discovery/reference tool.

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 link to pallets_per_trailer implies the intended usage (looking up valid trailer/pallet-id inputs), but the description never explicitly says when to call this versus the sibling, nor gives a prerequisite ordering. Usage is inferable rather than stated.

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