Skip to main content
Glama

get_my_usage

Show the signed-in Epic Video user's plan tier, plan tokens left in the current rolling 7-day window and this month, top-up (bonus) token balance, and per-second token rates (1 token/sec at 480p, 2 tokens/sec at 720p).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a solid job: it enumerates exactly what is returned (tier, rolling 7-day window, monthly total, bonus balance) and even quantifies the billing rate (1 token/sec at 480p, 2 at 720p). It stops short of stating auth/permission expectations or whether the values are cached/snapshot in time, which matters for a per-user account read.

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, front-loaded sentence with no filler; every clause names a distinct returned field and the parenthetical clarifications '(bonus)' and the per-second rates add real information rather than padding.

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?

For a zero-parameter read of account usage with no output schema, the description is nearly sufficient: it explains what values come back and how rates are computed. It leaves gaps around refresh/staleness of the rolling window and what the tier labels look like, which would help an agent interpret the result.

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 the baseline is 4. The description correctly implies all output is scoped to the authenticated caller, which is the only semantic an agent needs here.

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 uses the specific verb 'Show' and names the resource precisely: the signed-in user's plan tier, remaining plan tokens, top-up balance, and per-second rates. It is unambiguous what the tool returns, but it never references a sibling (e.g. get_job_status or list_my_videos) to delineate scope, so it falls short of the 5-level 'distinguishes from siblings' bar.

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 explicit when-to-use statement, no exclusions, and no alternatives named. The usage is only weakly implied by content ('plan tokens left', 'top-up balance'), so an agent must infer that this is a quota/account-status check rather than a media operation.

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.