SMKlog Parcel Shipping Rates

Shipping restrictions and battery rules

get_shipping_restrictions

Read-onlyIdempotent

Checks shipping restrictions and conditional item rules, including battery and international requirements, so you can confirm whether an item can be sent before requesting a quote.

Instructions

What SMKlog will not ship and what ships only with conditions: prohibited categories (weapons, drugs, counterfeit goods, money and valuables, living and perishable contents, dangerous goods, controlled exports), restricted ones (batteries, medicine, chemicals and aerosols, regulated natural products, age-restricted goods), the lithium battery rules the checkout applies (installed: UN3481 mark, ground; power banks: UN3480, ground only, up to 100 Wh and 5 lb; larger or lithium-metal batteries reviewed by hand), how to describe an item, and the international rules. The policy published at smklog.com/shipping-restrictions. No carrier call, no quote allowance.

Parameter rules:

No parameters.
A policy reference, not a verdict on one item: get_parcel_quote and the checkout check each item, by name too.
The lists are examples, not complete; carrier and destination rules can be stricter.

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": "get_shipping_restrictions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`summary`	Yes
`batteries`	Yes	The lithium battery rules, case by case
`prohibited`	Yes	Categories refused outright, with examples
`restricted`	Yes	Categories that ship only with conditions, or that the online checkout may refuse
`policy_page`	Yes	The published policy
`descriptions`	Yes	How to describe an item
`international`	Yes	Destinations and the customs declaration
`how_smklog_checks`	Yes	When SMKlog checks an item
`restricted_handling`	Yes	What a restricted item may need
`carrier_rules_control`	Yes	Who decides acceptance

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Nov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already declare this to be a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description then adds context that the annotations cannot: this is a static published policy, it makes no carrier call and returns no quote, and the listed categories are examples rather than a complete or authoritative set, since carrier and destination rules may be stricter. The one thing it does not say is explicit guidance on how to combine this policy with a per-item check, but the usage section largely covers that.

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

Conciseness4/5

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

The content is front-loaded: the opening clause says what the tool returns, and the trailing sentences add the important qualifiers. The list of categories is long but it is the substance an agent needs for judgment. The fragment 'The policy published at smklog.com/shipping-restrictions.' is slightly awkward phrasing, and one long sentence carries many clauses, but no sentence is wasted.

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

Completeness5/5

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

Because the tool is parameterless and has an output schema, the description does not need to cover return shape or parameter behavior. The context around annotations, mutation profile, non-exhaustiveness of the lists, and sibling routing is complete. An agent can confidently decide when to call this tool and what to expect from it.

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?

This tool has zero parameters, so the schema is already complete, and the baseline for a parameterless tool is 4 or higher. The description's 'No parameters' line is redundant with the schema rather than informative, so it does not earn a higher score. There is no parameter semantics to add and nothing misleading to subtract.

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

Purpose5/5

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

The description states a specific resource with a specific scope: the shipping restrictions and battery rules that SMKlog applies. It names the concrete content an agent will receive: prohibited categories, restricted categories, lithium-battery rules (UN3481/UN3480 and the Wh/lb limits), and international rules. It also distinguishes itself from its siblings: quote and checkout tools give per-item verdicts, while this tool gives the policy.

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

Usage Guidelines5/5

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

The description gives both the positive condition and the exclusion. It says to use this tool for the policy, not for an item-level verdict, and it names get_parcel_quote and the checkout path as the alternatives for that job. The line 'No carrier call, no quote allowance' clears up a likely false expectation. Nothing about when to use it is left to inference.

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

Deploy Server