Skip to main content
Glama

Get model performance metrics

get_model_performance_metrics
Read-onlyIdempotent

Retrieve token, latency, and call-count metrics for AI models, optionally filtered by model and timeframe, to analyze usage and performance.

Instructions

Read token, latency and call counts from Studio insightsLanguageModelUsage. Use get_insights_usage as the same data under a shorter name. Use get_conversation_patterns for chat shape. Read-only. Returns JSON totals and per-model rows.

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_model_performance_metrics"
  }
}

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. First observedv5.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so repeating 'Read-only' adds nothing; however the description does add that it returns JSON totals plus per-model rows, which tells the agent the shape of the payload. No permission, rate-limit, or scoping caveats are given, but for a read-only metrics tool that gap is small.

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 what is read and where it comes from, followed by disambiguation and return shape. The only slightly wasted sentence is 'Read-only', which duplicates an annotation.

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, full schema coverage, and an output schema present, the definition supplies everything needed to call the tool correctly. Only minor context, such as what 'Studio insightsLanguageModelUsage' implies about data scope, is 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?

Both parameters (model_id, timeframe) have full schema descriptions with defaults and semantics ('Omit for all models', 'Default 7d'). The description adds no parameter detail beyond the schema, so the baseline 3 applies.

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?

States a concrete verb and the exact metrics returned (token, latency, call counts) plus the underlying source (Studio insightsLanguageModelUsage), which no sibling name conveys. It also distinguishes itself from get_insights_usage and get_conversation_patterns by name.

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?

Explicitly routes the agent: use get_insights_usage for the same data under a shorter name, and get_conversation_patterns for chat shape. That is a concrete when-to-use-this-vs-alternative statement rather than implied guidance.

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