Skip to main content
Glama

Kite Discord Bot Builder

Get credit usage

get_usage
Read-only

Gets the credits an app used this month, how many its plan has per month, and the credits used each day and by commands, event listeners, scheduled tasks, webhooks, and messages. Credits reset at the start of each month in UTC, and an app that uses all of them stops running flows until then. get_blocks says what each block costs, and list_plans what other plans include.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>"
    },
    "name": "get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe ID of the app, from list_apps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: credits reset monthly in UTC and an app that exhausts them 'stops running flows until then,' which is operationally significant. It omits auth requirements and any latency or caching behavior, so not a 5.

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, both front-loaded with the payload description before the operational caveats and sibling references. The enumeration of breakdown categories is long but informative rather than redundant, though it is slightly dense in a single clause.

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 output schema, the description must explain return values and it does: monthly usage, plan allotment, per-day and per-category breakdowns. Combined with the reset timing and the exhaustion consequence, an agent has everything needed to call this correctly and interpret the result.

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?

There is a single parameter with 100% schema description coverage, including provenance ('from list_apps'), so the schema carries the parameter meaning. The description adds nothing about app_id beyond what the schema says, which is the expected baseline.

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 opens with a specific verb and resource — 'Gets the credits an app used this month' — and then enumerates exactly what is returned: plan allotment, daily usage, and breakdowns by commands, event listeners, scheduled tasks, webhooks, and messages. It is clearly distinguishable from get_blocks (per-block costs) and list_plans (plan catalog).

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 routes the agent to alternatives explicitly: 'get_blocks says what each block costs, and list_plans what other plans include,' which tells the agent when a related question belongs to a sibling. It does not state a negative condition (e.g., when not to call this tool), so it falls short of a full 5.

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.