Skip to main content
Glama

Check prohibited articles

check-prohibited-articles
Read-onlyIdempotent

Lists the items that are prohibited or restricted when posting from Sri Lanka to a destination country by international mail. Returns every entry for the country; compare the user's item against the descriptions yourself, as wording varies ("lithium batteries" vs "power banks"). Absence from the list is not a guarantee that an item is allowed.

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>"
    },
    "name": "check-prohibited-articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesDestination country, as an English name ("Australia") or two-letter ISO code ("AU").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, non-destructive, idempotent), and the description adds substantive behavioral context beyond that: the result is unfiltered, wording varies across entries, and absence is not proof of allowance. These are exactly the caveats an agent needs to interpret the output correctly.

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 sentences, front-loaded with purpose and followed by two useful interpretation caveats. There is no filler, and each sentence earns its place.

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

Completeness4/5

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

For a simple one-parameter read-only tool, the description is nearly complete: it explains that every entry is returned and how to compare against them. It does not detail the exact output structure or fields, and there is no output schema to fill that gap, so a minor completeness gap remains.

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?

There is a single required country parameter, and the schema already fully documents it as an English name or two-letter ISO code at 100% coverage. The description does not add any further parameter semantics, so the baseline of 3 applies.

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 verb and resource: it lists prohibited/restricted items for international mail from Sri Lanka to a destination country. The scope is precise enough to distinguish it from the pricing and post-office siblings without needing their schemas.

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?

It gives clear usage context by explaining that all entries are returned unfiltered and that the user must compare item wording manually. It also warns that absence is not a guarantee, which is important usage guidance. It does not explicitly name alternatives, but the sibling tools are unrelated, so this is still clear.

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