Skip to main content
Glama

Aurelmark

by io.github.Ishan73744
OverviewDiscussionsAdmin

EU trade defence measures by CN code

eu_trade_defence_measures
Read-onlyIdempotent

EU anti-dumping, countervailing and safeguard regulations as published in the Official Journal (from the Publications Office), each with the CN and TARIC codes found in its text, the countries of origin, the product, the action (provisional or definitive duty, amendment, extension, repeal, termination, registration, initiation) and the EUR-Lex link. Search by CN code (a regulation naming 7208 matches 72085120 and the reverse), date, instrument, action or country. Pass next_cursor back as cursor to page or to poll. Duty rates in force are in TARIC; the Official Journal is authoritative. Free.

Input Schema

NameRequiredDescriptionDefault
cnNoCN code, 4 to 10 digits, e.g. 7208 or 72085120
limitNoRegulations per page, 1 to 50 (default 20)
sinceNoRegulations dated on or after, YYYY-MM-DD
actionNoOne kind of action only
cursorNonext_cursor from a previous answer
countryNoCountry of origin, e.g. China
instrumentNoOne instrument only (steel: acts under the EU steel regime, Regulation 2026/1384)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "provisional",
-  "definitive",
-  "amendment",
-  "extension",
-  "repeal",
-  "termination",
-  "registration",
-  "initiation",
-  "other"
-]New value: +[
+  "provisional",
+  "definitive",
+  "amendment",
+  "extension",
+  "repeal",
+  "termination",
+  "registration",
+  "initiation",
+  "quota",
+  "other"
+]
    • changedInput schema / properties / instrument / description
      Previous value: -"One instrument only"New value: +"One instrument only (steel: acts under the EU steel regime, Regulation 2026/1384)"
    • changedInput schema / properties / instrument / enum
      Previous value: -[
-  "anti-dumping",
-  "countervailing",
-  "safeguard"
-]New value: +[
+  "anti-dumping",
+  "countervailing",
+  "safeguard",
+  "steel"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds non-obvious behaviour: bidirectional CN prefix matching ('a regulation naming 7208 matches 72085120 and the reverse'), cursor-based paging and polling, and the fact that access is free. Auth and rate-limit behaviour are not addressed, but that is a minor gap.

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?

A single dense paragraph, front-loaded with what the tool returns before covering search axes and paging. Every sentence carries information, though the opening clause is long and packs multiple claims that could be split for faster scanning.

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 usefully enumerates the returned fields (codes, origin countries, product, action, EUR-Lex link) and hints at the next_cursor field via the paging instruction. For a 7-parameter, 0-required filtering tool this is close to sufficient, missing only explicit default/sort behaviour.

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?

With 100% schema description coverage, the baseline is 3 and the schema already documents all seven parameters including enum values. The description earns above baseline by explaining matching semantics for 'cn' (partial vs full code) and the pagination contract for 'cursor', neither of which the schema conveys.

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?

States a specific resource (EU anti-dumping, countervailing and safeguard regulations from the Official Journal) and enumerates exactly what each result carries: CN/TARIC codes, countries of origin, product, action type and EUR-Lex link. An agent can distinguish this from eu_trade_quotas and the sanctions/cbam siblings without opening any schema.

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?

Gives concrete search axes ('Search by CN code, date, instrument, action or country') and operational instructions for pagination ('Pass next_cursor back as cursor to page or to poll'). It also clarifies the TARIC-vs-Official-Journal division of labour, but stops short of stating when this tool should not be used in favour of a 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