User Intuition

Interview Usage Stats

get_interview_usage_stats

Read-onlyIdempotent

Aggregate eligible non-test interview counts and billed units over a date range. The backend resolves the default app and a 30-day UTC range when omitted. The response includes the applied scope.

Input Schema

TableJSON Schema

Name	Required	Description
`app_id`	No	Optional app scope.
`cadence`	No
`end_date`	No	ISO date.
`start_date`	No	ISO date.
`organization_id`	No	Platform admins only: select an organization for usage totals.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Eligible interview counts, billed units, and resolved query scope.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / organization_id

Added value: +{
+  "description": "Platform admins only: select an organization for usage totals.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed7 schema fields changedSep 30, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / properties / result / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / result / properties / total_interviews / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / properties / total_interviews / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / result / properties / usage_stats / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 30, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare the safe read-only/idempotent profile, and the description adds real value beyond them: the non-test eligibility filter, the 30-day UTC default when dates are omitted, the backend-resolved default app, and that the applied scope is echoed back. It stops short of noting pagination or billing/eligibility edge cases.

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?

Three tight sentences, front-loaded with the aggregation semantics followed by defaults and response scope. Each sentence carries information; no filler or restatement of the title.

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 annotations covering safety, an output schema covering return shape, and 80% param coverage, the description supplies the missing operational context (defaults, filtering, echoed scope). Only cadence semantics and multi-app/multi-org behavior are left implicit.

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 coverage is 80%, so the schema largely documents the five parameters itself. The description adds the default-resolution behavior for date range and app scope, but says nothing about the cadence enum values or how start/end dates interact.

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 gives a specific verb (Aggregate) and resource (eligible non-test interview counts and billed units) scoped to a date range, so the agent knows exactly what is produced. It does not explicitly contrast itself with any sibling (e.g. get_fielding_progress or get_report_job), which keeps it short of a 5.

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 when-to-use or when-not-to-use guidance and no named alternative among the many reporting-adjacent siblings (get_fielding_progress, get_report_job, generate_report). The mention of backend default resolution is behavioral detail, not usage routing.

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

All User Intuition 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?