Skip to main content
Glama

usage_summary

Aggregates execution counts, success/failure, duration, and token usage by provider and model to monitor how subagents consume resources.

Instructions

プロバイダー/モデル別の実行回数・成否・所要時間・トークン等の使用量を集計する

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

Input Schema

NameRequiredDescriptionDefault
sinceNoISO日時
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden; it does disclose the metrics returned (counts, success/failure, duration, tokens), which is the most important behavioral fact. However, it says nothing about aggregation defaults (all-time when 'since' is absent), time zone handling, cost of the query, or whether the result is a single row or a grouped breakdown.

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?

A single front-loaded sentence that enumerates the measures efficiently with no filler. It could afford one more short clause given how little else is specified, but nothing in it is wasted.

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?

For a two-parameter, optional-parameter aggregation tool with no annotations and no output schema, the description covers the purpose and the metrics but omits defaults and the shape of the aggregation result. The mention of model-level grouping with no corresponding parameter is an unresolved gap an agent would notice.

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 50%: 'since' is documented in the schema as an ISO datetime, but 'provider' has no schema description and the description only implies it through 'プロバイダー別'. The description adds no format or filtering semantics beyond the schema, and notably says grouping is by provider/model while no model parameter exists.

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 names a specific verb (集計する/aggregate) and resource (使用量/usage), and enumerates the aggregated dimensions: execution count, success/failure, duration, and tokens, broken down by provider/model. That is far more specific than the bare name 'usage_summary', though it does not name any sibling tool to contrast with.

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 guidance on when to use this versus the run-level siblings such as get_run or list_models, and no mention of prerequisites or the default time window when 'since' is omitted. The reader must infer that this is the aggregate/reporting counterpart to the per-run tools.

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