Skip to main content
Glama

NovaPixel LexGrid

dual_use_export_control

Checks dual-use export control regimes and licensing requirements under Regulation (EU) 2021/821 (Annex I & II, UGEA EU001) and international sanctions.

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

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it leaves key traits unstated: whether the check is a safe read-only lookup, whether a failed/uncertain result is distinguishable from a negative one, and what the response contains (no output schema). It does add real value by pinning the legal basis (EU 2021/821 Annex I & II, UGEA EU001), which tells the agent the scope of regimes applied, but coverage limits and result shape are absent.

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 sentence with the action and regulatory scope front-loaded and no filler. The heavy citation list ('Annex I & II, UGEA EU001') is informative but slightly compresses readability.

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

Completeness3/5

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

For a 5-parameter compliance-decision tool with no annotations and no output schema, the description identifies the legal framework but says nothing about what a result looks like or how licensing outcomes are reported. An agent could call it correctly but would not know how to interpret the answer.

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%, including per-parameter descriptions and an enum for endUseSector, so the baseline of 3 applies. The description adds no meaning about how hsCode versus eccnCode are used, or what happens when only one of the two optional identification codes is supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Checks') and a precise resource ('dual-use export control regimes and licensing requirements'), plus the governing regulation and annexes, so the agent knows exactly what domain question this tool answers. It does not explicitly name or contrast itself with the siblings (cbam_embedded_emissions, incoterms_cost_allocator, taric_hs_validator), which keeps it from a 5.

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: the regulatory framing suggests it is the tool for export-control/licensing questions, but there is no statement of when to call it, what prerequisites exist (e.g. needing an ECCN first), or when another tool is the better choice. The agent must infer the trigger conditions.

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