Freedom Rave Wear

Estimate shipping

quote_shipping

Read-onlyIdempotent

Estimate guest shipping using country, merchandise subtotal in USD cents, and optional packed weight in grams. Final tax, duties, benefits and delivery timing are confirmed at checkout. No address needed.

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": {
      "country": "<country>",
      "subtotal_cents": "<subtotal_cents>"
    },
    "name": "quote_shipping"
  }
}

Input Schema

Name	Required	Description	Default
`country`	Yes
`weight_grams`	No
`subtotal_cents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely new behavioral context: the output is non-binding and several components are confirmed later at checkout, which prevents the agent from presenting it as a final total.

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?

Three short sentences. Inputs first, then the non-binding caveat, then the 'no address needed' constraint. No filler.

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

Completeness3/5

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

With no output schema, the description never indicates what an estimate returns (a cost figure? a currency? a breakdown?), which leaves the agent guessing about the response. Everything needed to call the tool is present, but not what to expect back.

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 0%, so the description must carry the load, and it does: it clarifies units for subtotal (USD cents) and weight (grams) and marks weight as optional, none of which the schema says. It omits the country code format (the schema's ^[A-Z]{2}$ pattern) and any weight-based rate tiers.

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?

Specific verb+resource: 'Estimate guest shipping' with the three inputs named. It is obviously distinct from all siblings (catalog/policy/review tools), though it doesn't explicitly say so.

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

Usage Guidelines4/5

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

States the prerequisite that matters for agent behavior ('No address needed') and the boundary that the result is an estimate with tax/duties/benefits/timing settled at checkout. No explicit named alternative, but the use context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Freedom Rave Wear 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?