EximAgent

Shipment source evidence

exim__evidence__show

Read-onlyIdempotent

Returns the raw source record behind one shipment, optionally with English-normalized fields. Use it to verify where a figure came from.

Input Schema

Name	Required	Description	Default
`id`	Yes	shipment id
`normalized`	No	also include English-normalized evidence fields

Output Schema

Name	Required	Description	Default
`data`	Yes
`stats`	No
`_debug`	No
`summary`	Yes
`warnings`	No
`nextActions`	Yes
`correlationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 13, 2026

removedInput schema / properties / --id

Removed value: -{
-  "description": "shipment id",
-  "type": "string"
-}

removedInput schema / properties / --normalized

Removed value: -{
-  "description": "also include English-normalized evidence fields",
-  "type": "boolean"
-}

addedInput schema / properties / id

Added value: +{
+  "description": "shipment id",
+  "maxLength": 8000,
+  "type": "string"
+}

addedInput schema / properties / normalized

Added value: +{
+  "description": "also include English-normalized evidence fields",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "--id"
-]New value: +[
+  "id"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "value0": {
+      "additionalProperties": false,
+      "properties": {
+        "normalizationConfidence": {
+          "type": "number"
+        },
+        "rawRecord": {
+          "type": "string"
+        },
+        "recordId": {
+          "type": "string"
+        },
+        "rejectReason": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "sourceFile": {
+          "type": "string"
+        },
+        "sourceRowNumber": {
+          "type": "integer"
+        },
+        "sourceSheet": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "normalizationConfidence",
+        "rawRecord",
+        "recordId",
+        "rejectReason",
+        "source",
+        "sourceFile",
+        "sourceRowNumber",
+        "sourceSheet"
+      ],
+      "type": "object"
+    },
+    "value1": {
+      "anyOf": [
+        {
+          "items": {
+            "type": [
+              "null",
+              "boolean",
+              "number",
+              "string",
+              "array",
+              "object"
+            ]
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value2": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/value3"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value3": {
+      "additionalProperties": false,
+      "properties": {
+        "command": {
+          "type": "string"
+        },
+        "cost": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "rationale": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "command",
+        "cost",
+        "label",
+        "rationale"
+      ],
+      "type": "object"
+    },
+    "value4": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value5": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/value6"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value6": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "value7": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": [
+              "null",
+              "boolean",
+              "number",
+              "string",
+              "array",
+              "object"
+            ]
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "additionalProperties": false,
+  "properties": {
+    "_debug": {
+      "$ref": "#/$defs/value7"
+    },
+    "correlationId": {
+      "type": "string"
+    },
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "context": {
+          "type": [
+            "null",
+            "boolean",
+            "number",
+            "string",
+            "array",
+            "object"
+          ]
+        },
+        "cursor": {
+          "type": "string"
+        },
+        "has_more": {
+          "type": "boolean"
+        },
+        "items": {
+          "anyOf": [
+            {
+              "items": {
+                "$ref": "#/$defs/value0"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "context",
+        "has_more",
+        "items"
+      ],
+      "type": "object"
+    },
+    "nextActions": {
+      "$ref": "#/$defs/value2"
+    },
+    "stats": {
+      "$ref": "#/$defs/value4"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "warnings": {
+      "$ref": "#/$defs/value5"
+    }
+  },
+  "required": [
+    "data",
+    "nextActions",
+    "summary"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only the return nature (raw source record, optionally normalized), which is modest added context rather than rich behavioral disclosure.

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?

Two sentences, zero waste. The core purpose is front-loaded and the usage hint follows immediately.

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 two-parameter, read-only tool with full schema coverage, an output schema and complete annotations, nothing an agent needs to invoke 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%, so both parameters are already documented by the schema. The phrase 'optionally with English-normalized fields' restates the schema's wording for `normalized` rather than adding new meaning, so the baseline 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?

States a specific verb and resource: it 'returns the raw source record behind one shipment.' The provenance framing ('verify where a figure came from') distinguishes it in spirit from retrieval siblings like exim__shipments__get, though it does not name an alternative explicitly.

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?

'Use it to verify where a figure came from' gives a clear use context. There is no explicit when-not condition or named sibling, but the intended scenario is unambiguous.

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

All EximAgent 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.