Skip to main content
Glama

get_utilization_stats

Retrieve GLM and Kimi Coding Plan usage and utilization metrics—including time elapsed, burn rate, projected utilization at reset, and quota waste—for one account or all enabled accounts.

Instructions

统计 GLM 与 Kimi Coding Plan 的使用量与利用率指标,包含窗口时间流逝比、消耗速率比(Burn Rate)、预计重置时最终利用率及额度浪费比例。

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

Input Schema

NameRequiredDescriptionDefault
account_idNo可选,指定统计单个账号 ID;不填则统计所有启用账号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses what metrics are computed but says nothing about data freshness, whether the call is expensive or rate-limited, whether it aggregates across accounts by default, or how the 'projected final utilization' is extrapolated.

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?

One front-loaded sentence that names the resource and then lists the metrics; no filler. The metric enumeration is dense but each item is substantive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the return metrics, which covers the main completeness gap. However, for a read-only stats tool with zero annotation coverage, it omits freshness/aggregation behavior and any cue for choosing it over the sibling.

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 100% and the single account_id parameter is already fully documented in the schema, including the 'all enabled accounts' default. The description adds no further meaning, so the baseline of 3 applies.

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-resource pair (統計 usage/utilization metrics) and scopes it to GLM and Kimi Coding Plan, enumerating the concrete metrics returned (time-elapsed ratio, burn rate, projected final utilization, quota waste). It does not distinguish this from the sibling query_balance, but the purpose itself is unambiguous.

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 statement of when to call this versus query_balance, no prerequisites, and no exclusions. The only usage-adjacent information is the account_id default behavior, which belongs to the parameter rather than to tool selection.

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

Deploy Server

Other Tools