Skip to main content
Glama

CutOptim Engine

Get API usage

get_usage
Read-onlyIdempotent

Free (needs an API key). Shows the plan, the calls used and left this month, and when the period ends. The account's current-month usage and quota. Read-only. Does not consume quota and does not send rate-limit headers. The period is the UTC calendar month.

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
envNo
planYes
usedYes
limitYes
trialNo
keyClassNo
keyPrefixYes
periodEndYes
remainingYes
contractVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / trial
      Added value: +{
      +  "properties": {
      +    "callsLimit": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "callsRemaining": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "callsUsed": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "endsAt": {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    "maxJobsLimit": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "maxJobsRemaining": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "maxJobsUsed": {
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "endsAt",
      +    "callsLimit",
      +    "callsUsed",
      +    "callsRemaining",
      +    "maxJobsLimit",
      +    "maxJobsUsed",
      +    "maxJobsRemaining"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations it discloses an auth prerequisite ('needs an API key'), a side-effect guarantee that survives the read-only hint ('does not consume quota'), rate-limit header behavior, and the exact reset semantics ('UTC calendar month'). These are precisely the traits an agent needs before deciding to poll this endpoint.

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?

The auth and quota facts are front-loaded and earn their place, but 'Shows the plan... when the period ends' and 'The account's current-month usage and quota' restate the same idea in adjacent sentences. Trimming the redundant restatement would tighten it without losing information.

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

Completeness5/5

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

With no parameters, an output schema covering return values, and annotations covering safety traits, the description adds exactly the missing layer: auth requirement, quota neutrality, and the UTC-month reset rule. Nothing needed to call it correctly is absent.

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 no parameter meaning to add; baseline is 4. The description correctly adds no parameter prose, avoiding noise.

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?

The description uses a concrete verb ('Shows') with enumerated resources: the plan, calls used and left this month, and when the period ends. That is unmistakably an account usage/quota reader, which no sibling (optimize_*, validate_*, get_job) could be confused with.

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 should call this to check remaining quota, but the description never says when to call it, how often, or what to do with the result. No alternatives exist among the siblings, so the omission is low-risk but still a gap.

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.