Skip to main content
Glama

Quota exhaustion predictor

privi_pro_quota_burn_rate
Read-only

Estimate when prepaid API credits will be exhausted at a known daily burn. PAID ONLY: 5 prepaid credits; production billing required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "remaining_credits": "<remaining_credits>",
      "daily_usage": "<daily_usage>"
    },
    "name": "privi_pro_quota_burn_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
daily_usageYes
remaining_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds genuinely new behavioral facts — a 5-credit cost and a production billing prerequisite. It does not say what the estimate looks like (days remaining, a date, or a confidence band), which is a real gap given no output schema.

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, zero filler, with the core purpose front-loaded and the paywall constraint isolated in its own clause. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-number estimator, the definition covers purpose, cost gate, and rough input mapping. Without an output schema, however, an agent still cannot predict the return value's shape or unit, and the unit ambiguity of daily_usage persists — gaps the description should have closed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden. It maps the two params to concepts — 'remaining_credits' as prepaid API credits and 'daily_usage' as daily burn — but gives no units, currency, or whether burn is credits-per-day or per-hour, leaving ambiguity for a pure numeric input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and outcome: 'Estimate when prepaid API credits will be exhausted at a known daily burn.' This distinguishes it from a snapshot-style sibling like privi_quota_remaining by framing it as a forward projection, though it never names the alternative explicitly.

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

Usage Guidelines3/5

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

'At a known daily burn' implies a precondition (you must already know the consumption rate), and 'PAID ONLY: 5 prepaid credits; production billing required' gates access. But there is no explicit statement of when to prefer this over privi_quota_remaining or privi_rate_budget, so routing is left to inference.

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.