Skip to main content
Glama

business_shipping_estimate

Read-onlyIdempotent

Shipping cost estimator

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": {
      "weightKg": "<weightKg>",
      "ratePerKg": "<ratePerKg>"
    },
    "name": "business_shipping_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoFixed base charge per parcel, for example 5.
weightKgYesParcel weight in kilograms, for example 2.5.
ratePerKgYesCarrier rate per kilogram, for example 3.2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / base / description
      Added value: +"Fixed base charge per parcel, for example 5."
    • addedInput schema / properties / ratePerKg / description
      Added value: +"Carrier rate per kilogram, for example 3.2."
    • addedInput schema / properties / weightKg / description
      Added value: +"Parcel weight in kilograms, for example 2.5."
  2. Changed1 schema field changed
    • addedInput schema / properties / base / minimum
      Added value: +0
  3. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that: it does not state the computation performed, whether `base` is optional, rounding/currency behavior, or units of the returned figure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short phrase, so there is no wasted wording, but it is under-specified rather than concise. It is front-loaded by default but carries almost no information payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small 3-parameter calculator with a fully described schema and no output schema, the missing piece is the formula and the optionality/effect of `base`, plus the unit/currency of the result. The description does not supply any of that, leaving an agent to guess at the computation semantics.

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% – all three parameters (base, weightKg, ratePerKg) are documented with units and examples in the schema. The description adds no extra parameter meaning, so baseline 3 applies; it does not explain the interaction between base and the per-kg rate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Shipping cost estimator" restates the tool name (business_shipping_estimate) as a noun phrase without a verb, formula, or scope. It does convey the general domain (shipping cost), but gives no detail about what is actually computed or how it differs from the many other business_* calculators in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The context is weakly implied by the name alone; an agent must infer that this is a pure arithmetic helper for parcel shipping costs.

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