AI MAXX Public Passports

Check catalogue coverage

catalogue_coverage

Read-onlyIdempotent

Read the actual countries, companies and record counts currently included in the public AI MAXX catalogue. Useful for checking whether the requested geography is covered before searching.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`scope`	Yes
`companies`	Yes
`country_codes`	Yes
`place_records`	Yes
`company_records`	Yes
`service_records`	Yes
`searchable_records`	Yes
`withheld_unverified_records`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "companies": {
+      "items": {
+        "properties": {
+          "country_code": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "passport_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "country_code",
+          "passport_id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "company_records": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "country_codes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "place_records": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "searchable_records": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "service_records": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "withheld_unverified_records": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "companies",
+    "country_codes",
+    "searchable_records",
+    "company_records",
+    "service_records",
+    "place_records",
+    "withheld_unverified_records",
+    "scope"
+  ],
+  "type": "object"
+}

First observedOct 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so the safety profile is fully covered. The description adds the scope of the data (countries, companies, record counts), but says nothing about freshness/latency or pagination that annotations don't cover.

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 tight sentences with no filler: the first states what is read, the second states why. The purpose is front-loaded and every clause earns its place.

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 no-parameter, read-only lookup with a full output schema and strong annotations, the description supplies the two things structured fields cannot: the domain of the returned inventory and the pre-search use case. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify or compensate for beyond correctly implying the call is argument-free.

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 names a specific verb (read) and resource (countries, companies and record counts in the public AI MAXX catalogue), so an agent understands exactly what it returns. It does not explicitly contrast itself with the consult_* search siblings, but the catalogue-inventory framing makes the distinction reasonably evident.

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?

Gives a concrete when-to-use: check whether the requested geography is covered before searching. That is clear routing guidance, though it stops short of naming which sibling to fall back on or stating any exclusion conditions.

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

All AI MAXX Public Passports 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.

Resources

Need Help?