Get a Sendle shipping quote from pickup and delivery postcodes plus package weight. Use it to compare delivery costs before booking a shipment.
Get a shipping quote from Sendle.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | ||
| weight_units | No | ||
| weight_value | Yes | ||
| pickup_suburb | No | ||
| pickup_country | No | ||
| delivery_suburb | No | ||
| pickup_postcode | Yes | ||
| delivery_country | No | ||
| delivery_postcode | Yes |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of credential requirements, rate limits, whether quotes are live or cached, or what happens with unsupported routes.
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 front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than efficient communication for a 9-parameter tool.
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?
With 9 parameters at zero schema coverage, no output schema, and no annotation coverage of inputs, the description is far too thin. An agent cannot confidently supply address, weight unit, or credential values from this text alone.
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?
Schema description coverage is 0% across 9 parameters, and the description provides no parameter meaning at all. Critical ambiguities such as weight_units default, country format, suburb optionality, and api_key handling are entirely undocumented.
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?
States a specific verb and resource (get a shipping quote) and names the provider (Sendle), which is enough for an agent to know it retrieves pricing rather than creating an order or tracking a parcel. It does not specify scope such as domestic vs international or what the quote covers.
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?
No guidance on when to use this versus siblings such as sendle_create_order, sendle_track_parcel, or other shipping/quote tools. No prerequisites (API key, supported countries, default weight units) are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.