Skip to main content
Glama

AIApply

Get AIApply credits and plan

get_credits_summary
Read-onlyIdempotent

Use this before queuing or sending work to check the connected user can still pay for it, or when they ask how many applications they have left. Reports the credit balance, whether auto-apply is active, the plan slug and the configured daily cap. The balance is what remains; the daily cap is not — nothing here says how many applications already went out today. It does not report prices, renewal dates or payment details, so send the user to AIApply for anything about billing itself. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
creditsYes
messageNoPresent when the billing state needs explaining. Follow it.
plan_slugNoNull when no plan could be read.
billing_stateYesknown, no_billing_record, or unreadable.
auto_apply_activeNoFalse when the subscription does not entitle applying.
daily_application_limitNoThe configured daily cap, not how much of it is left. Nothing here reports how many went out today, and multiplying it out to a weekly or monthly figure is never valid. Null when no queue exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive safety, and the description adds genuinely new behavior: the auth prerequisite and the fact that calling it without a signed-in user prompts sign-in, plus the critical caveat that the balance is remaining credit and not the number of applications sent today.

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?

Front-loaded with the primary use case, then followed by what it returns, what it does not return, and the auth prerequisite. Every sentence carries a distinct decision-relevant fact with no filler.

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?

For a zero-param read tool with an output schema and full annotation coverage, the remaining risks are misread semantics and missing auth, both of which the description addresses head-on.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. What it does describe (the returned fields) is arguably output-schema territory, but it usefully states the balance-vs-cap distinction.

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 and resource ('Reports the credit balance, whether auto-apply is active, the plan slug and the configured daily cap') and implicitly carves itself away from get_auto_apply_preferences and get_setup_status by enumerating exactly what it does and does not return.

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?

It gives an explicit trigger ('Use this before queuing or sending work to check the connected user can still pay for it') plus a conversational trigger ('when they ask how many applications they have left'), and an explicit exclusion routing billing questions to AIApply rather than this tool.

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