FACTRAIL

Assess EU Import (Beta)

factrail_assess

Read-onlyIdempotent

Use when you need a source-backed assessment of importing a product into the EU (tariff classification, duties, and related evidence). Returns an EvidenceEnvelope; import assessment is Beta and results expose source coverage and support levels.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`parameters`	Yes	Required + optional inputs for assess_import.
`assessment_type`	Yes	Currently only import is supported.

Output Schema

TableJSON Schema

Name	Required	Default
`facts`	Yes
`status`	Yes
`subject`	Yes
`coverage`	Yes
`evidence`	Yes
`conflicts`	Yes
`freshness`	Yes
`receipt_id`	No
`generated_at`	Yes
`schema_version`	No	1.2
`state_fingerprint`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

addedInput schema / properties / parameters / properties / assessment_date

Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional TARIC effective/simulation date; availability depends on the installed snapshot.",
+  "title": "Assessment Date"
+}

addedOutput schema / $defs / Fact / properties / support_level

Added value: +{
+  "$ref": "#/$defs/SupportLevel",
+  "default": "supported"
+}

addedOutput schema / $defs / SupportLevel

Added value: +{
+  "description": "How strongly a fact is supported, independent of numeric confidence.",
+  "enum": [
+    "authoritative",
+    "supported",
+    "derived_supported",
+    "derived_provisional",
+    "curated",
+    "caller_input"
+  ],
+  "title": "SupportLevel",
+  "type": "string"
+}

changedOutput schema / properties / schema_version / default
```
Previous value: -"1.1"New value: +"1.2"
```

AddedSep 27, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: it returns an EvidenceEnvelope, is Beta, and results expose source coverage and support levels — useful for interpreting reliability.

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?

Two sentences, front-loaded with the usage trigger and then the return/Beta caveat. Efficient and no wasted phrasing, though it is fairly terse for a tool with a large nested parameter object.

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?

An output schema exists, so return-value details need not be in the description. It mentions the EvidenceEnvelope type and Beta status, and the schema fully covers the 2-param nested input. The only real gap is disambiguation from the assess_import sibling.

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%, so the schema already documents every parameter (product, origin/destination country, currency, HS code, TARIC date, etc.). The description adds no additional input semantics or formats, so the baseline of 3 applies.

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 gives a specific verb (assess) and resource (importing a product into the EU), plus concrete scope: tariff classification, duties, and related evidence. It is clear on its own, but it never differentiates from the sibling tool named assess_import, which sounds nearly identical.

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?

"Use when you need a source-backed assessment of importing a product into the EU" gives a positive trigger condition. However, there are no when-not conditions and no routing away from the very similar sibling assess_import, so the agent gets only implied guidance on tool selection.

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

All FACTRAIL tools Inspect

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.