Skip to main content
Glama

Read my usage and limits

get_usage
Read-only

Get the user's own use of their plan: for each limited action, how many uses the current period counted, the allowance, and how many are available now; when a calendar period (day, month) resets, and for rolling windows (week, 30 days) when the oldest use drops out; bonus and pack credits, which buy uses beyond an allowance; and when a paid plan or trial ends. A resume generated in the background from text or answers (create_profile, the web onboarding) counts against resume_generation. Radar scans are not bought with bonus or pack credits. Bonus and pack credits are one shared pool: it is part of remaining for every action, so a credit spent on one action lowers remaining for all of them. A null limit or remaining means no limit. Reading job links (read_job_link) is not listed here; its own limit is in read_job_link. The actions listed are the same ones get_pricing gives limits for. Plan prices and the limits of other plans are in get_pricing.

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
planYesThe user's current tier: 'free' | 'sprint' | 'career'.
itemsYesOne row per action the plan limits.
creditsYesBonus and pack credits, which buy uses beyond an action's allowance on any plan; null when there are none.
plan_ends_atYesISO 8601 UTC moment the paid plan or trial ends and the account returns to free; null on free. Whether a plan renews is the auto_renews of its SKU in get_pricing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / $defs / UsageCredits / properties / remaining
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "description": "Credits left in this month's pool; null on plans without a pool.",
      -  "title": "Remaining"
      -}
    • removedOutput schema / $defs / UsageCredits / properties / resets_at
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "description": "ISO 8601 UTC moment the pool refills to total; null on plans without a pool.",
      -  "title": "Resets At"
      -}
    • removedOutput schema / $defs / UsageCredits / properties / total
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "description": "The pool's monthly size on the current plan; null on plans without a pool.",
      -  "title": "Total"
      -}
    • changedOutput schema / $defs / UsageCredits / required
      Previous value: -[
      -  "remaining",
      -  "total",
      -  "resets_at",
      -  "bonus",
      -  "pack_credits"
      -]New value: +[
      +  "bonus",
      +  "pack_credits"
      +]
    • changedOutput schema / $defs / UsageItem / properties / credit_cost / description
      Previous value: -"Credits one use of this action is worth. chat_message, interview_session and radar_scan never draw on the monthly credit pool, and radar_scan is not bought with bonus or pack credits either."New value: +"Bonus or pack credits one use of this action costs once its allowance is spent. radar_scan is not bought with credits."
    • changedOutput schema / $defs / UsageItem / properties / remaining / description
      Previous value: -"Uses available right now: what the allowance has left, plus what the bonus and pack credits in `credits` can buy of this action beyond it, capped by the monthly credit pool on plans that have one. So remaining can be larger than limit. Null means unlimited."New value: +"Uses available right now: what the allowance has left, plus what the bonus and pack credits in `credits` can buy of this action beyond it. So remaining can be larger than limit. Null means unlimited."
    • changedOutput schema / properties / credits / description
      Previous value: -"The monthly credit pool on plans that meter one (free, sprint), and bonus and pack credits on any plan; null when there is neither."New value: +"Bonus and pack credits, which buy uses beyond an action's allowance on any plan; null when there are none."
  2. Changed1 schema field changed
    • changedOutput schema / $defs / UsageItem / properties / action / description
      Previous value: -"Action type, e.g. 'vacancy_analysis' | 'resume_generation' | 'chat_message'. 'pdf_download' counts new PDF files; downloading the file already made for an unchanged resume is not counted."New value: +"Action type, e.g. 'vacancy_analysis' | 'resume_generation' | 'chat_message'."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint=false/destructiveHint=false, so the safety profile is covered. Beyond that the description discloses genuinely non-obvious behavior: null means unlimited, bonus and pack credits form one shared pool so spending on one action lowers remaining for all, radar scans are excluded from credit purchases, and background-generated resumes count against resume_generation. The one gap is that it does not restate freshness/latency of the counters, though nothing suggests that matters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the first sentence is an extremely long run-on that packs five distinct claims together, and the credit pool is explained twice ('which buy uses beyond an allowance' then re-stated in the shared-pool sentences). Content mostly earns its place, yet the structure could be split into short bulleted facts for far easier scanning.

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?

An output schema exists, so return-value explanation is not owed, and the description instead supplies the interpretation rules an agent cannot infer from the shape: null equals no limit, shared credit pool, exclusion of job links, and correspondence with get_pricing's action list. Complete for a zero-parameter read tool.

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 nothing for the description to disambiguate; baseline 4 applies. It uses the space instead on return semantics, which the output schema partly covers.

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 resource ('Get the user's own use of their plan') and then enumerates exactly what is returned: per-action counts, allowances, remaining, reset timing, credit pools, and plan/trial expiry. It explicitly distinguishes itself from siblings get_pricing (prices and other plans' limits) and read_job_link (its own limit lives elsewhere).

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?

Routing is clear: use this for the caller's own usage and limits, get_pricing for plan prices and other plans' limits, read_job_link for job-link limits. It stops short of an explicit 'use this when the user asks about how many generations they have left' framing, but the boundary with alternatives is stated precisely.

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.