Skip to main content
Glama

quota-reservation-check

Would this request fit in the remaining quota, given a snapshot and pending reservations? (snapshot-bound) — Computes available quota from a caller-supplied snapshot (limit, used, reserved) minus the unexpired pending reservations and says whether a requested amount fits. This is a read of the numbers you supply as of snapshotAt: it reserves nothing, so concurrent consumers can still use the quota before you do, and every response says so. A stale snapshot gives unknown, not pass; a window that ended at

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": {
      "quota": "<quota>",
      "request": "<request>",
      "snapshotAt": "<snapshotAt>",
      "asOf": "<asOf>"
    },
    "name": "quota-reservation-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYesRFC 3339 instant of the decision (no clock is read).
quotaYes
pendingNo
requestYes
snapshotAtYesRFC 3339 instant the quota numbers were read.
maxSnapshotAgeSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load and does well: it discloses that the operation is a pure read, that it races with concurrent consumers, and that a stale snapshot yields 'unknown' rather than 'pass'. The final sentence is truncated ('a window that ended at '), so one behavioral rule—what happens to an expired window—is cut off, which for an unannotated tool is a real disclosure gap.

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 structure is good—framing question first, then the mechanics, then the caveats—and most sentences earn their place. But the definition ends mid-word ('a window that ended at '), leaving a broken clause, and the dense parenthetical stacking in the second sentence makes it harder to scan than necessary.

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 six-parameter tool with nested objects and no output schema, the description covers the safety model and the staleness semantics, which is the hard part. Yet the truncation drops a stated outcome case, and nothing describes the shape of the response beyond 'every response says so', so an agent cannot fully predict what it receives on an expired window or a missing snapshot.

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?

Schema description coverage is only 33% across six parameters, but the description compensates by stating the computation model (limit, used, reserved minus unexpired pending) and anchoring it to the snapshot instant, which goes well beyond field names. It does not explain maxSnapshotAgeSeconds, the parameter that actually governs the 'stale snapshot gives unknown' behavior, nor clarify the relationship between asOf and the per-reservation expiresAt.

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 opens with a precise question ('Would this request fit in the remaining quota...') and then states the verb and resource explicitly: computes available quota from a caller-supplied snapshot minus unexpired pending reservations. The parenthetical '(snapshot-bound)' and the phrase 'it reserves nothing' separate it from mutating quota tools such as allocate, so an agent can distinguish it without reading the schema.

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?

It gives useful context by implying the tool is a non-binding pre-flight read ('it reserves nothing, so concurrent consumers can still use the quota before you do'), which hints at when the result is advisory rather than authoritative. However, it never names an alternative tool or states an explicit condition for choosing reservation-checking over reserving, leaving the agent to infer the boundary with allocate.

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