Skip to main content
Glama

Get my usage and limits

get_usage
Read-onlyIdempotent

START HERE for 'how many calls or credits do I have left'. COST: free, no API key required, and it does not count against the keyless 10 calls per day (it is subject to the per-minute pace limit like every call). Returns your tier (keyless, free, starter, pro, enterprise or agent), calls used and remaining for the current window (daily for keyless, monthly for plans), profile pulls (pulls_used, pulls_limit, pulls_remaining and when that window resets, pulls_resets_at; a pull is one get_fund call or one LP row from search_lps), credits remaining for agent keys, when the call window resets (resets_at), and your per-minute pace limit. Never charges anything. Cost: free

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the call is free, requires no API key, does not consume the keyless 10/day allowance, and is still subject to the per-minute pace limit. Those are non-obvious billing and throttling behaviors an agent could not infer from the annotations.

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 key qualifier ('START HERE') and cost information are front-loaded, and the return-field enumeration is dense but useful. The trailing 'Never charges anything. Cost: free' repeats the opening cost statement and could be cut 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?

There is no output schema, so the description must carry the return contract, and it does: tier enum, calls used/remaining per window type, profile pull fields, credits, resets_at, and pace limit. Nothing an agent needs to interpret the response 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 are no semantics to explain; the description correctly spends no space on inputs. Baseline for a 0-param tool is 4.

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 names a specific verb+resource ('Returns your tier... calls used and remaining') and anchors it to the exact question it answers ('how many calls or credits do I have left'). No sibling tool overlaps this purpose, so an agent can select it immediately.

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 explicitly says 'START HERE' for quota questions and explains the cost/rate implications that matter when deciding to call it. It does not point to alternatives (e.g., check_lp_coverage, which relates to the 'pulls' concept it mentions), so routing guidance is clear but not exhaustive.

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.