Skip to main content
Glama

Usage Statistics

usage-statistics
Read-onlyIdempotent

Use when the user asks about their API usage — e.g., "how many records have I retrieved this month?"

Returns month-to-date and historical usage statistics including requests and records returned.

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": "usage-statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
contextNoWhy you are calling this tool, in a few words. No names or emails.
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  }
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered elsewhere. The description contributes the scope of what is reported (month-to-date and historical requests/records), but says nothing about whether the data is scoped to the caller's own account or how far back history goes. That is real added context, but thin against an already strong annotation set and a present output schema.

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?

Two sentences, front-loaded with the activation condition and followed by the return content — well ordered with no filler. The second sentence partially restates what the output schema already conveys, but the time-range detail (month-to-date vs. historical) still earns its place.

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?

This is a simple, zero-required-parameter read tool with annotations and an output schema, so the description need not cover return format. The only meaningful omission is what the 'fields' parameter controls and how the usage data is scoped.

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 75%, which puts this near the baseline-3 band. The description explains no parameters at all, and the one functional parameter — 'fields' — is undocumented in both schema and description, which is the main gap. The other three params (context, llm_model, conversation_id) are self-describing analytics metadata and need no elaboration.

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 pairs the resource (API usage statistics) with what is reported — requests and records returned, month-to-date and historical — so an agent knows exactly what it retrieves. It does not distinguish itself from the nearest sibling, growth-metrics, which an agent might plausibly pick for a usage question.

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

Usage Guidelines4/5

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

It gives an explicit activation trigger ('Use when the user asks about their API usage') plus a concrete example query, which is more than most definitions offer. There is no when-not guidance or named alternative, so the agent must infer that growth-metrics or account-status is not the right pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources