Skip to main content
Glama

get_usage

Read-only

Returns today's and this month's generation counts, estimated costs, budget caps, and the number of jobs currently in progress.

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": "get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without description help. The description adds the substantive behavioral detail that the response covers cost estimates, caps, and in-flight job counts. It does not clarify side-effect-freedom beyond the annotation, nor whether the cap is a hard limit that blocks generation — a detail an agent would want before deciding to generate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the returned metrics with no preamble, hedging, or redundant restatement of the tool name. Every clause names a distinct data point the caller will receive.

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 an output schema present and annotations covering read-only semantics, the description need not explain return shape, and it correctly stays at the summary level. Minor residual gaps: it does not state the timezone/period boundary for '오늘' (today) or whether cost is in a fixed currency, both of which affect interpreting the numbers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The schema being an empty object matches the description's implicit 'just call it' contract.

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 ('돌려준다' / returns) and enumerates the exact resource contents: today's and this month's generation counts, estimated cost, cap, and in-progress task count. That is far more informative than the bare name get_usage. It does not explicitly contrast with siblings, but none of the listed siblings (generate_video, estimate_video, get_video_status, etc.) overlap with usage/quota reporting, so confusion risk is low.

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?

Usage is only implied: an agent can infer it is for checking quota, spend, and active jobs, presumably before generating or when asked about cost. There is no explicit when-to-use statement, no prerequisite note, and no mention of alternatives such as estimate_video for per-job cost forecasting — a genuinely useful distinction given the sibling set.

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