AI Agent Analytics

Validate an Agent Analytics installation

validate_installation

Read-onlyIdempotent

Verify that product_id has an active ingestion credential, an accepted customer_test setup event, and an accepted event visible to Agent Analytics. Use this immediately after setup; do not use it for broader diagnostics or history, use get_connection_health. product_id is the only parameter and validation always uses a fixed 30-day health window. Requires analytics:read; this proves setup plumbing only, creates no production activity or payment, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product_id`	Yes	Exact AI Agent Analytics product/property ID returned by list_products. Do not pass a product name, URL, or organization ID.

Output Schema

TableJSON Schema

Name	Required	Description
`schema`	Yes	Delegated response schema identifier.
`product`	Yes
`validation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 19, 2026

changedOutput schema / properties / product / properties / id / description

Previous value: -"Product/property ID."New value: +"Tenant-checked product/property ID."

changedOutput schema / properties / product / properties / time_zone / description

Previous value: -"IANA time zone used for product-local daily interpretation."New value: +"IANA time zone used for product-local interpretation."

changedOutput schema / properties / schema / description

Previous value: -"Response schema identifier."New value: +"Delegated response schema identifier."

addedOutput schema / properties / validation / additionalProperties
```
Added value: +{}
```

removedOutput schema / properties / validation / description

Removed value: -"Installation-verification checks, verified scope, unresolved claims, and next action."

addedOutput schema / properties / validation / properties

Added value: +{
+  "checks": {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "evidence": {
+          "description": "Human-readable evidence for the check result.",
+          "type": "string"
+        },
+        "id": {
+          "description": "Stable check identifier.",
+          "type": "string"
+        },
+        "passed": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "id",
+        "passed",
+        "evidence"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "integrity": {
+    "additionalProperties": {},
+    "properties": {
+      "absence_of_a_business_stage_is_not_treated_as_broken_instrumentation": {
+        "type": "boolean"
+      },
+      "customer_test_never_counts_as_real_agent": {
+        "type": "boolean"
+      },
+      "no_payment_required": {
+        "type": "boolean"
+      },
+      "no_synthetic_production_activity_created_by_validation": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "no_payment_required",
+      "customer_test_never_counts_as_real_agent",
+      "absence_of_a_business_stage_is_not_treated_as_broken_instrumentation",
+      "no_synthetic_production_activity_created_by_validation"
+    ],
+    "type": "object"
+  },
+  "next": {
+    "description": "Next recommended setup action.",
+    "type": "string"
+  },
+  "not_verified_by_this_check": {
+    "description": "Commercial or behavioral claims this check explicitly does not prove.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "schema": {
+    "description": "Installation-validation schema identifier.",
+    "type": "string"
+  },
+  "state": {
+    "enum": [
+      "verified",
+      "not_yet_verified"
+    ],
+    "type": "string"
+  },
+  "verified": {
+    "description": "True only when all setup-plumbing checks pass.",
+    "type": "boolean"
+  },
+  "verified_scope": {
+    "description": "Claims actually verified by this check.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / properties / validation / required

Added value: +[
+  "schema",
+  "verified",
+  "state",
+  "checks",
+  "verified_scope",
+  "not_verified_by_this_check",
+  "next",
+  "integrity"
+]

addedOutput schema / properties / validation / type
```
Added value: +"object"
```

Changed2 schema fields changedSep 19, 2026

changedInput schema / properties / product_id / description

Previous value: -"AI Agent Analytics product/property ID from list_products."New value: +"Exact AI Agent Analytics product/property ID returned by list_products. Do not pass a product name, URL, or organization ID."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "product": {
+      "additionalProperties": {},
+      "properties": {
+        "id": {
+          "description": "Product/property ID.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Product name.",
+          "type": "string"
+        },
+        "time_zone": {
+          "description": "IANA time zone used for product-local daily interpretation.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "time_zone"
+      ],
+      "type": "object"
+    },
+    "schema": {
+      "description": "Response schema identifier.",
+      "type": "string"
+    },
+    "validation": {
+      "description": "Installation-verification checks, verified scope, unresolved claims, and next action."
+    }
+  },
+  "required": [
+    "schema",
+    "product",
+    "validation"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context beyond these: the required permission (analytics:read), that it creates no production activity or payment, the fixed 30-day health window, and the shared MCP rate limit (300 calls/60s) with HTTP 429 and Retry-After. None of this contradicts the annotations, and it meaningfully aids the agent in safe and correct invocation.

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?

Four sentences, each earning its place: the primary purpose, the usage constraint with alternative, parameter and window context, and critical operational limits. Front-loaded with the core verification objective, no filler or repetition.

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?

Given the tool has an output schema (which covers return values) and rich annotations, the description covers all required invocation context: purpose, scope, exclusions, permissions, rate limits, and fixed operational window. An agent has everything needed to call this correctly.

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%, and the schema already details product_id with pattern and explicit guidance (exact ID from list_products, not a name/URL/org ID). The description mentions product_id is the only parameter and the fixed 30-day window, but these are operational notes, not new parameter semantics. Baseline of 3 is appropriate given the schema already carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Verify') and the resource (installation setup state of product_id), and explicitly distinguishes itself from get_connection_health by noting it is not for broader diagnostics or history. This makes the purpose unambiguous and clearly differentiated from siblings.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('immediately after setup') and when-not-to-use ('do not use it for broader diagnostics or history, use get_connection_health'). Naming the exact alternative and the condition for choosing it gives agents clear routing guidance.

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

All AI Agent Analytics 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?