agent-bev Library

get_rulebook

The trade rulebook for one country by its two-letter code (uk for the United Kingdom): market status, who can trade, customs and duty, labelling, age and sale limits, protected names, GTIN authority, and open items and as-of date; each section lists its official sources, and a part with no official source says "Not yet sourced".

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": {
      "code": "<code>"
    },
    "name": "get_rulebook"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	two-letter country code as the Library writes it, for example es, uk, jp

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior beyond the schema: each section lists official sources, unsourced parts explicitly return 'Not yet sourced', and results carry an as-of date that warns about staleness. It omits any mention of unknown-code behavior or size/latency, keeping it short of a 5.

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?

One front-loaded sentence that leads with the resource and then the returned sections; every clause adds information. It is dense and slightly run-on with the semicolon-plus-sources clause, but nothing is redundant.

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?

There is no output schema, so the description must characterize the return value, and it does so by enumerating the sections plus the source and as-of-date metadata. For a one-parameter lookup that is nearly complete; only failure modes for an invalid code are unaddressed.

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?

With 100% schema description coverage on the single 'code' parameter, the schema already defines the input. The description reinforces the semantics ('by its two-letter code', 'as the Library writes it') and gives the uk example, but adds no format rules or edge cases beyond what the schema states.

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 names a specific verb+resource ('The trade rulebook for one country') and enumerates the payload sections (market status, who can trade, customs and duty, labelling, age limits, protected names, GTIN authority, open items, as-of date), so an agent can tell exactly what comes back and that this differs from the sibling list_countries, which only lists countries.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this when it needs trade rules for a single country. There is no explicit when-to-use/when-not guidance and no routing to list_countries for discovering valid codes, though the parenthetical 'uk for the United Kingdom' does clarify the expected input form.

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

All agent-bev Library 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?