Skip to main content
Glama

Plan, limits and usage

my_usage
Read-onlyIdempotent

Shows which plan the connected API key is on, the request limits that apply, the expiry date and today's request count. Check it before a long series of calls to see how much allowance remains (a Free key gets 100 requests a day), or after a call failed with rate_limited or key_expired.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the description does not need to re-establish safety. It adds real behavioral context beyond them: the concrete Free-tier allowance of 100 requests/day and the fact that the response is keyed to the connected API key's plan state. It stops short of saying when the daily counter resets or whether the count is live versus cached, which is the one detail an agent might still want.

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?

Two sentences: the first enumerates what is returned, the second gives the usage triggers. The quota figure is parenthetically placed so it does not interrupt the trigger logic, and no sentence is redundant.

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?

There is no output schema, but the description compensates by enumerating the four returned fields (plan, limits, expiry, today's count), so an agent knows what it will get back. For a zero-parameter read tool with annotations covering the safety profile, nothing needed for correct invocation is missing.

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 semantics to explain and the baseline of 4 applies. The description correctly describes a no-argument introspection call rather than implying hidden inputs.

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?

States a specific verb and a concrete resource set: plan, request limits, expiry date, and today's request count, scoped to the connected API key. No sibling in the list (board_sports, feed_health, find_matches, match_prices, price_moves, search_pinnradar_docs, upcoming_lines) overlaps with account/usage introspection, so it is trivially distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use triggers on both sides: proactively before a long series of calls, and reactively after a failure carrying rate_limited or key_expired. The reactive trigger even names the exact error codes that should route the agent here, which is unusually actionable.

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.

Resources