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

Name	Required	Description
`app_id`	No	Optional app scope.
`cadence`	No
`end_date`	No	ISO date.
`start_date`	No	ISO date.
`organization_id`	No	Select an organization you belong to for usage totals. Users can belong to multiple organizations.

Output 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 22, 2026

changedInput schema / properties / organization_id / description

Previous value: -"Platform admins only: select an organization for usage totals."New value: +"Select an organization you belong to for usage totals. Users can belong to multiple organizations."

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

A4.3/5.0

Behavior4/5

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

Annotations already declare this as a safe, idempotent read. The description adds meaningful behavior beyond annotations: eligibility excludes test interviews, omitted app/date values default to the backend app and a 30-day UTC range, and the applied scope is returned.

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 short sentences, zero waste, and the core aggregation purpose is front-loaded. Default behavior is included only where it materially affects invocation.

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?

With an output schema present and annotations covering the safety profile, the description supplies the remaining call-critical context: what is counted, default scope resolution, and confirmation that the response reports applied scope. No critical invocation information 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?

Schema coverage is high at 80%, so most parameters are already documented. The description adds useful semantics for omitted app_id and date parameters by stating that the backend resolves the default app and a 30-day UTC range; cadence remains undocumented beyond its enum.

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 gives a specific verb ("Aggregate") and precise resources ("eligible non-test interview counts and billed units"), with date-range scoping. It clearly identifies a usage-statistics tool rather than interview CRUD or listing tools in the sibling set.

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

Usage Guidelines3/5

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

The purpose implies usage reporting, and the description explains default app/date resolution. However, it does not explicitly say when to use this instead of related tools like get_interview, list_interviews, or get_account, nor does it state exclusions.

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?