ARCNM

Check Quota

check_quota

Read-onlyIdempotent

Check this organization's calculation allowance for the current period: included, used and remaining calculations, whether more runs are blocked or billed as overage, the remaining overage budget and whether runs are paused. Use it before starting several billable calculations with upload_and_quote or quote_part. Read-only and free.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	No
`used`	No
`bonus`	No	Thank-you calculations granted on top of the plan this window.
`window`	No	'month' or 'year'.
`guidance`	Yes
`included`	No	Calculations included per window.
`rollover`	No	Unused calculations carried in from last window.
`effective`	No	Ceiling this window (included + rollover + bonus).
`remaining`	No	Calculations still available this window.
`over_quota`	No
`hard_capped`	No	True: over-quota runs park as blocked. False: they bill as overage.
`window_start`	No	ISO 8601 start of the current quota window.
`overage_cents`	No	Price of one calculation beyond the included volume, in cents.
`payment_blocked`	No	True when billing is suspended and nothing will run.
`wallet_overdrawn`	No	True when the prepaid balance has reached its hard floor — calculations are paused and further runs park as 'blocked' until the balance is topped up.
`overage_cap_cents`	No	Monthly overage spend cap in cents, or null when uncapped. Bounds what over-quota runs may cost.
`spend_cap_blocked`	No	True when the overage cap is reached and set to pause — further over-quota runs park as blocked.
`has_payment_method`	No	Whether a payment method is on file; a 'wallet' plan needs one for calculations beyond the included volume.
`overage_settlement`	No	How overage is paid: 'wallet' (a prepaid balance that is the ceiling) or 'invoice' (contracted, billed in arrears).
`overage_spend_cents`	No	Overage already billed this calendar month, in cents.
`wallet_balance_cents`	No	Prepaid balance in cents ('wallet' settlement only).
`wallet_overdraft_cents`	No	How far the prepaid balance is below zero, in cents.
`wallet_funded_calculations`	No	How many more overage calculations the current balance covers; beyond it, calculations park as 'blocked'.
`wallet_overdraft_floor_cents`	No	Hard floor on the prepaid balance, in cents; the balance can never go below its negation.
`overage_budget_remaining_cents`	No	Overage spend still inside the cap, in cents; null when uncapped.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 12, 2026

changedOutput schema / description

Previous value: -"This organization's remaining calculation quota and monthly overage\nbudget — check before a bulk run so you can upgrade the plan (or raise the\noverage cap) up front instead of parking calcs as 'blocked'."New value: +"This organization's calculation allowance for the current period and\nits overage budget: how many calculations are included, used and\nremaining, and what happens to a run beyond the allowance."

changedOutput schema / properties / has_payment_method / description

Previous value: -"Whether a card is on file. Required before any calculation beyond the included volume on a 'wallet' plan."New value: +"Whether a payment method is on file; a 'wallet' plan needs one for calculations beyond the included volume."

changedOutput schema / properties / overage_settlement / description

Previous value: -"How overage is paid: 'wallet' (prepaid — the balance is the ceiling, top up to continue) or 'invoice' (contracted, billed in arrears)."New value: +"How overage is paid: 'wallet' (a prepaid balance that is the ceiling) or 'invoice' (contracted, billed in arrears)."

changedOutput schema / properties / wallet_funded_calculations / description

Previous value: -"How many more overage calculations the balance covers. Check this before a bulk run — past it, calculations park as 'blocked'."New value: +"How many more overage calculations the current balance covers; beyond it, calculations park as 'blocked'."

changedOutput schema / properties / wallet_overdrawn / description

Previous value: -"True when the prepaid balance has reached its hard floor — calculations are paused and further runs park as 'blocked' until the balance is topped up. Check this before a bulk run."New value: +"True when the prepaid balance has reached its hard floor — calculations are paused and further runs park as 'blocked' until the balance is topped up."

AddedOct 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuine context not in the annotations: the operation is free of charge, and it discloses the operational state it surfaces (runs blocked, billed as overage, paused). It does not add auth or rate-limit detail, but that is a minor gap given the annotation coverage.

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 the purpose and ending with the routing guidance. The middle clause enumerates every returned field, which is somewhat list-heavy and partly duplicates the output schema, but it is not padded with 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?

With no parameters, an output schema, and rich annotations, the definition supplies everything an agent needs: what is measured, that it is free and read-only, and when to call it relative to upload_and_quote and quote_part. Nothing required for correct invocation 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 is nothing to document and the schema trivially covers 100% of the surface. Baseline of 4 applies since the description has no parameter semantics to add or omit.

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 (check the organization's calculation allowance for the current period) and enumerates exactly what is reported: included/used/remaining calculations, blocking vs overage billing, remaining overage budget, and pause state. That scope is distinguishable from siblings like list_calculations or explain_cost without opening any schema.

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?

Gives an explicit trigger and names the alternatives: 'Use it before starting several billable calculations with upload_and_quote or quote_part.' This is a clear when-to-use rule tied to concrete sibling tools, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ARCNM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.