Skip to main content
Glama

dual_use_export_control

Read-onlyIdempotent

[Deterministic trade compliance engine. Pure calculation, read-only, side-effect free]. Evaluates dual-use export control regimes and licensing requirements under Regulation (EU) 2021/821 (Annex I & II, Union General Export Authorisations EU001-EU008) and destination sanctions embargoes (e.g. Russia, Iran). Usage: Use this tool to verify whether high-tech, cyber-surveillance, encryption, or advanced electronic items require individual export authorization before shipment. Returns: JSON object with { isControlled: boolean, licensingRequirement: 'NONE' | 'INDIVIDUAL_LICENSE' | 'GLOBAL_LICENSE' | 'PROHIBITED', applicableUgea: string | null, legalBasis: string, warningFlags: string[] }.

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": {
      "destinationCountry": "<destinationCountry>",
      "endUseSector": "<endUseSector>"
    },
    "name": "dual_use_export_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
hsCodeNo6-digit or 8-digit HS Code (e.g. 85423190)
eccnCodeNoExport Control Classification Number (e.g. 5A002, 4A003, 3A001, 1C350)
endUseSectorYesDeclared end-use sector
isMilitaryEndUserNoWhether the recipient is a military or defense entity
destinationCountryYes2-letter ISO country code of destination (e.g. US, RU, CN, CH, GB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, yet the description adds substantive context: 'Deterministic trade compliance engine. Pure calculation, read-only, side-effect free', which tells the agent results are stable and safe to retry. It also discloses the return contract (isControlled, licensingRequirement enum, applicableUgea, legalBasis, warningFlags), which no output schema provides.

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 labeled blocks — bracket tag, Usage, Returns — front-load the constraint and the call trigger with no filler sentences. Every line, including the return-value enumeration, gives the agent information it cannot get from structured fields.

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 deterministic, schema-rich, 5-parameter tool with no output schema, the definition supplies purpose, regulatory scope, call trigger, and a full return shape including enum values. Nothing needed to invoke or interpret it correctly is missing.

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?

Schema description coverage is 100% with examples for hsCode, eccnCode and an enum for endUseSector, so the schema already carries the parameter semantics. The description mentions item categories only in prose and adds no format or precedence guidance (e.g. whether eccnCode overrides hsCode when both are supplied).

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 verb and domain ('Evaluates dual-use export control regimes and licensing requirements') and names the exact regulatory instruments (EU 2021/821 Annex I & II, UGAs EU001-EU008) plus embargo regimes. An agent can distinguish this from taric_hs_validator (HS validation) and cbam_embedded_emissions 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?

The 'Usage' line gives an explicit decision context: verify whether high-tech, cyber-surveillance, encryption, or advanced electronic items need individual authorization before shipment. It does not name alternatives or states exclusions, so it falls short of a 5.

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