EximAgent

Rank collection by a question

exim__collection__analyze

Read-onlyIdempotent

Ranks every company in a collection against a plain-language question, with a 0-100 score and one-sentence reasoning each.

Input Schema

Name	Required	Description
`question`	Yes	Plain-language analytical question to rank against
`collectionId`	Yes	Collection name or id
`rankingCriteria`	No	Optional explicit weighting hints

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.

Changed8 schema fields changedOct 13, 2026

removedInput schema / properties / --collectionId

Removed value: -{
-  "description": "Collection name or id",
-  "type": "string"
-}

removedInput schema / properties / --question

Removed value: -{
-  "description": "Plain-language analytical question to rank against",
-  "pattern": "[^\\t\\n\\v\\f\\r\\x85\\p{Z}]",
-  "type": "string"
-}

removedInput schema / properties / --rankingCriteria

Removed value: -{
-  "description": "Optional explicit weighting hints",
-  "type": "string"
-}

addedInput schema / properties / collectionId

Added value: +{
+  "description": "Collection name or id",
+  "maxLength": 8000,
+  "type": "string"
+}

addedInput schema / properties / question

Added value: +{
+  "description": "Plain-language analytical question to rank against",
+  "maxLength": 8000,
+  "pattern": "[^\\t\\n\\v\\f\\r\\x85\\p{Z}]",
+  "type": "string"
+}

addedInput schema / properties / rankingCriteria

Added value: +{
+  "description": "Optional explicit weighting hints",
+  "maxLength": 8000,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "--collectionId",
-  "--question"
-]New value: +[
+  "collectionId",
+  "question"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "value0": {
+      "additionalProperties": false,
+      "properties": {
+        "companyId": {
+          "type": "string"
+        },
+        "companyName": {
+          "type": "string"
+        },
+        "evidence": {
+          "$ref": "#/$defs/value1"
+        },
+        "rank": {
+          "type": "integer"
+        },
+        "reasoning": {
+          "type": "string"
+        },
+        "score": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "companyId",
+        "companyName",
+        "evidence",
+        "rank",
+        "reasoning",
+        "score"
+      ],
+      "type": "object"
+    },
+    "value1": {
+      "additionalProperties": false,
+      "properties": {
+        "country": {
+          "type": "string"
+        },
+        "description": {
+          "type": "string"
+        },
+        "matchReasons": {
+          "$ref": "#/$defs/value2"
+        },
+        "priority": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "tradePotential": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "tradePotentialReasoning": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "country",
+        "description",
+        "matchReasons",
+        "tradePotential",
+        "tradePotentialReasoning"
+      ],
+      "type": "object"
+    },
+    "value2": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value3": {
+      "anyOf": [
+        {
+          "items": {
+            "type": [
+              "null",
+              "boolean",
+              "number",
+              "string",
+              "array",
+              "object"
+            ]
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value4": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/value5"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value5": {
+      "additionalProperties": false,
+      "properties": {
+        "command": {
+          "type": "string"
+        },
+        "cost": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "rationale": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "command",
+        "cost",
+        "label",
+        "rationale"
+      ],
+      "type": "object"
+    },
+    "value6": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value7": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/$defs/value8"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "value8": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "value9": {
+      "anyOf": [
+        {
+          "additionalProperties": {
+            "type": [
+              "null",
+              "boolean",
+              "number",
+              "string",
+              "array",
+              "object"
+            ]
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "additionalProperties": false,
+  "properties": {
+    "_debug": {
+      "$ref": "#/$defs/value9"
+    },
+    "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/value4"
+    },
+    "stats": {
+      "$ref": "#/$defs/value6"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "warnings": {
+      "$ref": "#/$defs/value7"
+    }
+  },
+  "required": [
+    "data",
+    "nextActions",
+    "summary"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that every company is scored and each gets one-sentence reasoning, but with an output schema present even this is partly redundant, and it says nothing about cost, latency, or limits on collection size.

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?

A single front-loaded sentence that conveys action, scope, input, and output with zero filler. Nothing to trim.

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?

With full schema coverage, an output schema, and annotations covering the safety profile, the description is nearly sufficient. The only real gap is routing guidance versus the other ranking tools (profile-match__rank, employees__rank), which the definition never addresses.

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 collectionId, question, and rankingCriteria; baseline is 3. The description restates 'plain-language question' but adds no syntax, format, or weighting semantics, and never mentions the optional rankingCriteria parameter.

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 (ranks), resource (every company in a collection), and the driving input (a plain-language question), plus the output shape (0-100 score + one-sentence reasoning). This distinguishes it from collection__get/list and from the profile-match__rank / employees__rank siblings, though no sibling is named 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?

No when-to-use or when-not-to-use guidance, no alternatives named, and no prerequisites stated (e.g., that the collection must already exist and contain companies). The agent must infer the scenario from the purpose sentence alone.

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.