ftl_quoteQuote a full truckload (53' dry van). Only origin, destination, and date required.
| Name | Required | Description | Default |
|---|---|---|---|
| pallets | No | Pallets (optional, display only) | |
| commodity | No | Commodity description | |
| origin_zip | Yes | 5-digit US ZIP code | |
| pickup_date | Yes | Pickup date YYYY-MM-DD | |
| destination_zip | Yes | 5-digit US ZIP code | |
| weight_lbs_per_pallet | No | Weight per pallet (optional) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the agent knows the tool is safe. The description does not contradict annotations and adds a minor behavioral cue by stating minimal input requirements, but it does not elaborate on the quote generation process or output behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that is front-loaded with the core action ('Quote a full truckload') and immediately clarifies the essential scope and required fields. No wasted words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks details about the output format (e.g., price, transit time) and does not disambiguate from the sibling tool 'van_quote', which may cause confusion. Given no output schema, more information on return values would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the base expectation is a 3. The description adds value by clarifying that only origin, destination, and date are required, implicitly marking other parameters as optional. This helps the agent understand which fields are essential for the quote.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states that the tool quotes a full truckload (53' dry van) and highlights the minimal required fields (origin, destination, date). This clearly distinguishes it from siblings like ltl_quote or box_truck_quote.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly signals when to use this tool by specifying 'full truckload (53' dry van)' and emphasizing that only three fields are required. It lacks explicit exclusions or alternative recommendations, but the context is clear enough for an AI agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose. Overlapping tools like batch_quote, compare_modes, and per-mode quote tools are clearly differentiated by their scope and use cases. Batch vs single booking are also distinct.
Most tools follow a verb_noun pattern in snake_case (e.g., batch_quote, list_bookings). A few like 'analytics' and 'events' are noun-only but still clear. Overall consistent with minor deviations.
26 tools cover a broad logistics domain including quoting, booking, tracking, documents, and account management. While slightly heavy, each tool serves a specific function and the count is reasonable for the scope.
The tool set appears complete for freight operations: all major modes quoted, single/batch/multi-stop booking, tracking, documents, invoices, history, and account management. No obvious missing CRUD operations.