Skip to main content
Glama

MCPFax Agent Continuity

by com.mcpscores
OverviewDiscussionsAdmin

What has this work cost me

budget_check
Idempotent

What this unit of work has actually cost across every session, with a per-label breakdown and a lifetime total. If a limit is set (or you pass one here) we report over_limit — WE REPORT, WE NEVER BLOCK: enforcement is the caller's decision and we will not pretend to an authority we do not have. Amounts come back byte-exact in the units you supplied. $0.002 ONLY when there is recorded history in the window; an empty ledger tells you so and costs nothing, and asking again for an unchanged total is free. Costs $0.002 USDC per call via x402 on Base, and ONLY when count >= 1 in the requested window, and this exact total has not been billed before; otherwise the same call returns the full answer and settles nothing. Authenticate with Authorization: Bearer , or pass agent_key as an argument if your host cannot set headers. Equivalent HTTP route: POST /v1/budget/check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional. Compare against this limit for this call only, instead of the one stored on the scope. Example: '1.00'.
scopeYesThe unit of work. Example: 'permit-review-2026-08'.
agent_keyNoYour agent_secret, if your MCP host cannot set the Authorization header. Prefer the header.
window_secondsNoHow far back to total. Default 86400 (1 day), max 31536000 (365 days). The lifetime total is always reported alongside it. Example: '86400'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_key / examples
      Added value: +[
+  "the agent_secret that register returned"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / examples
      Added value: +[
+  "1.00"
+]
    • addedInput schema / properties / scope / examples
      Added value: +[
+  "permit-review-2026-08"
+]
    • addedInput schema / properties / window_seconds / examples
      Added value: +[
+  86400
+]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses billing side effects, idempotent free repeats for unchanged totals, the no-blocking enforcement promise, byte-exact amounts, empty-ledger behavior, and authentication requirements. This goes well beyond what the annotations convey and matches the idempotentHint and non-destructive flags.

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?

The description is long but dense, with the core purpose front-loaded and billing behavior structured clearly. Every sentence contributes operational information, though the emphatic no-blocking rhetoric could be tightened without losing meaning.

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

Completeness4/5

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

For a paid tool with no output schema, the description explains return semantics (per-label breakdown, lifetime total, over_limit, empty ledger, byte-exact amounts), billing, auth, and equivalent HTTP route. It stops short of enumerating exact response fields, but an agent has enough to invoke and interpret 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?

Schema coverage is 100%, and all parameters already have descriptions. The tool description adds operational meaning on top: limit is a per-call override, window_seconds has default and max values, and agent_key is a header fallback. This is meaningful value beyond the schema.

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 states a clear verb, resource, and result: inspect what a unit of work has actually cost, with a per-label breakdown and lifetime total. It is immediately distinguishable from siblings like budget_record, work_status, and heartbeat because it focuses on cost accounting rather than recording, scheduling, or lifecycle state.

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?

The description gives strong usage context: call it to see accumulated cost, optionally pass a limit to get over_limit, and expect it to never block. It does not explicitly name which sibling to use instead, but the domain and billing details make the targeted use case clear.

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

All MCPFax Agent Continuity toolsInspect
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.

Resources