EximAgent

Re-verify one contact email

exim__enrich__contact

Re-verifies one saved contact's email and fills it in when found.

Input Schema

Name	Required	Description	Default
`mail`	No	Existing email address to verify
`employeeId`	No	Employee ID whose existing email to verify

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.

Changed5 schema fields changedOct 13, 2026

removedInput schema / properties / --employeeId

Removed value: -{
-  "description": "Employee ID whose email to re-verify",
-  "type": "string"
-}

addedInput schema / properties / employeeId

Added value: +{
+  "description": "Employee ID whose existing email to verify",
+  "format": "uuid",
+  "maxLength": 8000,
+  "type": "string"
+}

addedInput schema / properties / mail

Added value: +{
+  "description": "Existing email address to verify",
+  "maxLength": 8000,
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "--employeeId"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "value0": {
+      "additionalProperties": false,
+      "properties": {
+        "employeeId": {
+          "type": "string"
+        },
+        "mail": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "status": {
+          "type": "string"
+        },
+        "verificationSource": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "employeeId",
+        "status",
+        "verificationSource"
+      ],
+      "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

B3.2/5.0

Behavior3/5

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

Annotations already declare the mutation and openness profile (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive). The description adds genuine context beyond them: 'fills it in when found' discloses a conditional write-back and that the field may not be populated. It does not cover failure behavior, auth needs, or what happens when the email cannot be verified.

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 efficient sentence with the verb and outcome front-loaded and no filler. Nothing is wasted, though it is arguably terse for a tool with a conditional-update behavior worth expanding.

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?

An output schema exists, so return values needn't be explained, and the annotations carry the safety profile. Still missing: guidance on choosing between its two optional parameters (required count is 0, which is ambiguous for a tool that needs an identifier) and any pointer to the plural batch 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 both 'mail' and 'employeeId' are already documented in the schema. The description adds no meaning about how the two relate or whether one should be supplied, though the baseline for high coverage is adequate here.

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: 'Re-verifies one saved contact's email'. The scope word 'one' implicitly distinguishes it from the plural sibling exim__enrich__contacts, and 'saved contact' clarifies it operates on existing records. It stops short of naming the sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The phrase 'saved contact' weakly implies it applies to already-stored contacts rather than new ones, but an agent must infer when to pick this over exim__enrich__contacts or exim__enrich__company.

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.