Skip to main content
Glama

Primary Source Commodities

Remaining Credits on This Key

account.quota
Read-onlyIdempotent

How many credits the calling Pro key has left in the current billing period, and which scopes it may read. FREE, and requires an API key in the Authorization header — x402 callers pay per request and have no quota to report. Use it to decide whether to spend on a bundle or a pack before calling 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": "account.quota"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planNo
scopesYesEmpty means unrestricted
credits_usedYes
billing_periodYes
credits_includedNo
credits_remainingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the description correctly spends its words elsewhere: it discloses that the call is FREE, that an API key is required in the Authorization header, and that x402 pay-per-request callers fall outside the quota model entirely. That auth and cost context is real value beyond the annotations; only error/expiry behavior for a missing or invalid key is left unstated.

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?

Two sentences, front-loaded with what is returned, then auth/cost caveats, then the decision use case. Dense but every clause carries information; the 'which scopes it may read' clause sits slightly awkwardly inside the first sentence rather than as its own thought.

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 shape need not be described. For a trivial no-parameter read, the description covers the account model (Pro key vs x402), billing period scoping, price, and auth requirement, leaving nothing an agent needs in order to call it correctly.

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 beyond the schema's empty object. Baseline for a no-parameter tool applies.

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 resource and metric: remaining credits on the calling Pro key within the current billing period, plus the scopes it may read. An agent immediately knows this is a quota/entitlement read, not a pricing or trade tool, which separates it from the bundle/pack siblings named by implication.

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?

Gives a concrete decision context: use before spending on a bundle or a pack, and states that x402 callers have no quota to report, which is effectively a when-not-to-use rule. It stops short of naming the specific sibling tool(s) to call after checking quota, so the routing is implied rather than explicit.

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