Skip to main content
Glama
Sign In

Aurelmark

by io.github.Ishan73744
OverviewDiscussionsAdmin

List CBAM default-value countries

cbam_list_countries
Read-onlyIdempotent

Returns the origin countries that have their own table in the official CBAM default-values act, as ISO code and name, with the regulation source. Use it to pick a country code before calling cbam_get_default_values; it returns no emission values itself, and countries not listed use OTHER there. No inputs. Output: countries[] (code, name) and source. Changes only when the bundled official act is updated. Terms: read-only; MCP calls are never charged. Without a key, metered routes give 10 successful answers a day free, as short samples (up to 3 records, without file proof, history or paging cursor) where a paid HTTP address exists (unmetered routes are unlimited); errors do not count. On the paid HTTP routes, errors are free, and so are empty answers except a sanctions name search with no match when every loaded list it checks is fresh (lists not loaded yet are named in the answer). An optional API key keeps its prepaid-credit policy. When the free answers run out, the error names the HTTP alternative.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavior: no emission values returned, OTHER fallback semantics, and that the data changes only when the bundled act is updated. The rate-limit, auth, and error-accounting disclosure goes well beyond the annotations, though the sanctions-name-search clause is unrelated noise that blurs the signal.

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

Conciseness2/5

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

The core purpose and routing guidance are well front-loaded in the first two sentences, but they are followed by a long metering/credit paragraph whose sanctions-search exception has nothing to do with listing CBAM countries. That tail roughly doubles the length without helping the agent select or invoke this tool.

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?

For a parameterless tool with no output schema, the description supplies the return shape ('countries[] (code, name) and source'), the freshness model, and the downstream fallback, which is everything needed to call it and interpret the result.

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?

Zero parameters, so the baseline is 4; the description correctly states 'No inputs', which matches the empty schema and additionalProperties: false. Nothing further is needed or missing here.

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 first sentence names a specific verb and resource ('Returns the origin countries that have their own table in the official CBAM default-values act') plus the exact payload (ISO code, name, regulation source). It explicitly contrasts with the sibling cbam_get_default_values, so an agent can route between the two without opening either schema.

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?

Gives an explicit when-to-use ('pick a country code before calling cbam_get_default_values'), an explicit when-not ('it returns no emission values itself'), and the fallback rule ('countries not listed use OTHER there'). No inference is required to choose this tool over its sibling.

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

All Aurelmark toolsInspect
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