Skip to main content
Glama

Export Control

by dev.toolstop

Which control columns a destination carries

lookup_country
Read-only

Return the Commerce Country Chart row for a destination: which of the sixteen control columns are marked, with each reason expanded. Use this to see how heavily controlled a destination is, or to check the chart's spelling of a country before another lookup. Special-controls destinations such as Cuba, Iran, North Korea and Syria return embargoed with a referral, because the chart does not govern them and reading a blank row as permission would be badly wrong. A marked column means a licence is required for items controlled for that reason; it says nothing about any particular item until you pair it with an ECCN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesDestination country name, e.g. Germany.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesOutcome of the lookup. Only `ok` carries an answer. `embargoed` means the chart does not govern the destination. `indeterminate` means the entry has no country-chart control in this data and the chart cannot answer for it, which is not the same as no licence being required. `ambiguous_country` means the name matched more than one row and you must ask which was meant.
columnsNoMarked control columns, each with its reason code and expanded name.
countryNoThe chart row that was matched.
referralNoWhere to look instead, for a special-controls destination.
footnotesNoChart footnotes on this row, each with its number and text. They carry conditions the grid cannot show, such as the Russia and Belarus sanctions and the Crimea controls, and they can change the answer.
candidatesNoPossible destinations, when the name matched more than one row.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, the description discloses important behavioral details: the 'embargoed' result with referral for special destinations, the meaning of marked columns (licence required), and the limitation that it says nothing about specific items until paired with an ECCN. This exceeds the annotation coverage and prevents misinterpretation.

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?

The description is dense but every sentence adds value, including the special-case caveat and the clarification about licence meaning. It is front-loaded with the primary purpose and structured logically from general behavior to exceptions.

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?

Given the tool's complexity (sixteen columns, special cases, integration with ECCN lookups), the description covers the key behaviors and usage context thoroughly. The presence of an output schema means return details need not be elaborated, and the special-controls warning addresses a critical edge case that could otherwise lead to unsafe conclusions.

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?

The schema already fully describes the single 'country' parameter with 'Destination country name' and an example. The description adds minor context about checking spelling before other lookups, but this is not essential to parameter usage. With 100% schema coverage, baseline is 3.

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 states the tool returns the Commerce Country Chart row for a destination, specifying exactly what data it provides (which of sixteen control columns are marked, with reasons expanded). This clearly differentiates it from sibling tools by focusing on the chart rather than license checks, reason codes, or ECCN lookups.

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?

Explicit usage guidance is given: 'Use this to see how heavily controlled a destination is, or to check the chart's spelling of a country before another lookup.' It also warns about special-controls destinations, implying when this tool is not appropriate for those cases and when a referral is provided.

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

All Export Control toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.9/5.0
Disambiguation5/5

Each tool has a distinct role: check_export_license combines ECCN and country for a verdict, lookup_eccn provides entry details, lookup_country provides destination chart rows, and explain_reason_code expands code definitions. There is no overlap that would cause an agent to select the wrong tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: check_export_license, explain_reason_code, lookup_country, lookup_eccn. The convention is uniform and predictable.

Tool Count5/5

Four tools is well-scoped for the focused purpose of export control license determination. Each tool earns its place as part of a coherent workflow, and the count is within the ideal range.

Completeness5/5

For the stated scope (Commerce Country Chart-based license checking), the tool set covers the full workflow: look up ECCN, look up country, check license, and expand reason codes. The descriptions explicitly note limitations, so there are no surprising gaps within the server's intended domain.

Resources