Skip to main content
Glama

Get insights usage

get_insights_usage
Read-onlyIdempotent

Read Studio insights usage totals for one model or all models over a chosen timeframe. Returns read-only JSON totals and per-model breakdowns for usage and performance analysis.

Instructions

Read Studio insights usage for one model or all models. Same data as get_model_performance_metrics. Read-only. Returns JSON totals and models.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_insights_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idNoOptional model id to filter. Omit for all models.
timeframeNoWindow such as 7d, 30d or all. Default 7d.7d

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv6.2.1
    • addedInput schema / properties / model_id / description
      Added value: +"Optional model id to filter. Omit for all models."
    • addedInput schema / properties / timeframe / description
      Added value: +"Window such as 7d, 30d or all. Default 7d."
  2. Addedv6.1.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so "Read-only" in the description merely restates structured data. The genuinely additive content is the equivalence to get_model_performance_metrics, which tells the agent results should match another tool. Return-shape text ("JSON totals and models") is largely redundant given an output schema exists, and pagination or rate limits are unaddressed.

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?

Four short sentences, front-loaded with the core purpose and scoping before the sibling comparison. Nothing is padded, though "Returns JSON totals and models" is low-value given an output schema and could be dropped. Very slightly clipped at the cost of clarity around what "insights usage" actually measures.

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?

This is a simple two-optional-parameter read tool with full annotation coverage and an output schema, so return values need no explanation. The description covers scope (single vs all models), the sibling equivalence, and the read-only nature — nothing an agent needs in order to invoke it correctly is missing. Additional detail would be redundant rather than helpful.

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 both parameters are already fully documented (model_id optional, "Omit for all models"; timeframe default 7d). The description's phrase "for one model or all models" echoes the model_id semantics but adds no format, valid-range, or interaction detail beyond the schema. This is the expected baseline-3 case where the schema does the work.

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 uses a specific verb and resource ("Read Studio insights usage") and states the scope precisely: one model or all models. It also names the equivalent sibling, get_model_performance_metrics, so an agent can tell it is the parallel read path rather than a different concept. It stops short of a 5 because "Studio insights usage" is only loosely defined and the equivalence to the sibling is asserted rather than characterized.

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?

By noting it returns the same data as get_model_performance_metrics, the description implicitly signals the two are interchangeable and steers the agent away from expecting different results. However, it never says explicitly when to pick this tool over that sibling, nor does it state any exclusion or prerequisite. Usage is implied, not prescribed.

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