Skip to main content
Glama

Screen import requirements

screen_import_requirements
Read-onlyIdempotent

Access: API key required. Screen declared product and entry facts against the published import-requirement families (FDA including prior notice, CPSC, EPA, FCC, APHIS Lacey Act plant declaration, soil import permits, and plant-pest import permits, NHTSA, OFAC rough diamonds, AMS shell eggs, TTB tobacco, TTB alcohol beverage imports, Commerce steel and aluminum import licenses, DOE natural gas import authorization, State Section 609 shrimp (DS-2031), CBP marking, CBP vessel Importer Security Filing, EPA composite wood formaldehyde (TSCA Title VI), FDA radiation-emitting electronic products, FDA acidified and low-acid canned food filings, FDA 361-only HCT/P imports, EPA HFC and ozone-depleting substance bulk imports, FTC textile, wool, fur and care labeling, FTC energy and water use labels, FWS wildlife import ports, clearance and declarations, CBP cultural property import restrictions, ATF explosives imports, DEA listed chemical and tableting or encapsulating machine imports, NRC nuclear equipment and material import licenses, the NOAA Seafood Import Monitoring Program and International Fisheries Trade Permit, the NOAA tuna and driftnet-fish Fisheries Certificate of Origin, ITAR temporary imports of defense articles (DSP-61 and 22 CFR 123.4), EPA hazardous waste imports (40 CFR part 262 subpart H), DOE energy conservation certification of imported appliances and equipment, CITES import documents and permits, the forced labor import prohibition (section 307, UFLPA, withhold release orders), the OFAC Cuba, Iran and North Korea import prohibitions, section 337 exclusion and seizure orders, recorded trademark counterfeit, copying and gray market restrictions, recorded copyright piratical article restrictions, CPSC refusal of admission of consumer products, FDA refusal of admission and reconditioning, EPA fuel and fuel additive imports, the CBP importer identity number and entry bond, FCC equipment authorization at import, seafood and juice HACCP importer verification, FDA animal food CGMP and preventive controls, medicated feed and veterinary feed directive drugs, FDA human food labeling, major food allergens, nutrition labeling and dietary supplements, FDA food additives, color additives and food contact substances, TSCA significant new use notification for imports, quota-class merchandise at entry, APHIS fruit and vegetable imports, Endangered Species Act import prohibitions, FDA medical device imports, FDA drug establishment registration and listing for imported drugs, ICTS connected vehicle hardware and software (BIS), pre-Columbian monumental sculpture and murals, EPA pesticide and device imports and the Notice of Arrival, DEA controlled substance import permits, declarations and transshipment, ATF firearms, ammunition and Munitions Import List import permits, AMS organic import certificates, CDC import permits for infectious agents and vectors, CDC admission of dogs, cats, turtles, nonhuman primates and African rodents, FDA cosmetics facility registration, product listing and label contact under MoCRA, FDA tobacco product premarket authorization, flavor and modified risk standards, user fees, registration and labeling, EPA vehicle and engine emissions imports, CPSC product safety rules, lead and phthalate limits, third-party testing and children's product tracking labels, PHMSA hazardous materials imports including lithium cells and batteries, OSHA approval of workplace electrical equipment by a nationally recognized testing laboratory, APHIS live animal, animal product, veterinary biologic and organism imports, NHTSA Registered Importer conformance and import eligibility of nonconforming vehicles, FAA import acceptance and airworthiness of aviation products, Coast Guard boat labels, hull identification numbers and equipment approval, entry user fees and federal excise taxes payable at entry) for one entry date, the same operation as POST /v1/import-requirements/screen. Each family answers requirement_identified with actions, not_applicable_to_this_rule, needs_information with the exact questions to answer, outside_coverage naming the undecided provision, or unavailable outside the reviewed source dates. Omit a fact you do not know; never answer no for an unknown. Name destination_states (ISO 3166-2 codes; US-CA is supported) to also receive state_requirements for the states the goods will be sold or distributed in: California Proposition 65 consumer product warnings and California alcoholic beverage importation through a licensed importer. State requirements apply to sale or distribution in the state and are not enforced at the border; without destination_states, state_requirements is empty and the federal results are the same. This is not import clearance, and evidence is not verified.

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": {
      "as_of": "<as_of>",
      "facts": "<facts>"
    },
    "name": "screen_import_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofYesISO date in YYYY-MM-DD form
factsYes
rule_idsNo
destination_statesNoU.S. states (ISO 3166-2) the goods will be sold or distributed in; their state requirements are returned in state_requirements. Omit to assess no state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, so the bar is lower, yet the description adds real substance: API key requirement, the five possible per-family outcomes (requirement_identified, not_applicable_to_this_rule, needs_information, outside_coverage, unavailable) with their meanings, and the caveat that evidence is not verified. It omits latency, pagination and any note on rule_ids behavior, so it stops short of a 5.

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 central paragraph is a single sentence enumerating roughly sixty regulatory regimes, which is far beyond what an agent needs to select or invoke the tool and pushes the actionable instructions (omit unknown facts, destination_states semantics, not-clearance caveat) to the tail. The useful content exists but is buried rather than front-loaded and is grossly oversized.

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?

For a tool with four parameters and a very large nested facts schema, the definition covers purpose, authentication, per-family response semantics, state-level behavior and explicit limitations, and there is no output schema so return-format explanation is not required. The unaddressed rule_ids parameter and the unexplained relationship to sibling entry-assessment tools are the remaining gaps.

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 description clarifies as_of ('for one entry date'), destination_states ('ISO 3166-2 codes; US-CA is supported', state results apply to sale or distribution and are not border-enforced, absent states yields empty state_requirements), and gives a materially useful rule for facts (omit unknowns, never answer no for an unknown). However rule_ids — a 47-item filter — is never mentioned, and with 50% schema coverage across a very large nested facts object the description does not fully compensate.

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 opening clause states a specific verb and resource ('Screen declared product and entry facts against the published import-requirement families') and pins the identity to a concrete API operation ('the same operation as POST /v1/import-requirements/screen'). An agent can tell this is a requirements-screen rather than a duty calculator or entry auditor, though no sibling is named explicitly and the purpose sentence is overwhelmed by the multi-hundred-word regulatory enumeration that follows.

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 context is implied rather than stated: 'for one entry date', 'Omit a fact you do not know; never answer no for an unknown', and 'Name destination_states ... to also receive state_requirements'. It also bounds scope ('This is not import clearance, and evidence is not verified'), which helps exclude misuse. But there is no explicit when-to-use versus alternatives such as assess_import_entry, and no prerequisites beyond the API key.

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