Skip to main content
Glama

agent-offset-clearinghouse

by io.github.jdhart81

buy_offset_budget

Money-denominated offset purchase: retire the maximum cheapest-first verified mass whose exact cost fits inside budget_minor (never overspends). Built for callers whose restoration obligation is a currency amount — e.g. a revenue share accrued in a ledger. Idempotent on purchase_id; dry_run=true previews without mutating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyerYes
dry_runNo
purchase_idYes
budget_minorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4/5.0
Behavior4/5

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

Discloses key behaviors: never overspends, selects cheapest-first, idempotent on purchase_id, dry_run previews without mutation. Since no annotations exist, description carries full burden and addresses it well.

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, front-loaded with core operation, use case, and key properties. No redundant words; every sentence adds value.

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?

Covers main behavior and use case but lacks details on edge cases (e.g., insufficient budget) and parameter specifics. Output schema exists but description does not reference it. Adequate for basic understanding.

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

Parameters2/5

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

Schema has 0% description coverage. Description mentions budget_minor as cost limit and purchase_id for idempotency, but does not explain buyer or dry_run semantics in detail. Leaves some parameter meaning unclear.

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 clearly states the tool performs a budget-constrained offset purchase, selecting the cheapest verified mass that fits within budget_minor without overspending. It distinguishes itself from siblings by specifying money-denominated obligation and idempotency.

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?

Explicitly says it's built for callers with a currency amount obligation, e.g., revenue share. Provides context for when to use this tool, but does not explicitly contrast with sibling 'buy_offset'.

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

All agent-offset-clearinghouse toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct operation (e.g., book vs. list_credit vs. verra_supply; buy_offset vs. buy_offset_budget; certify_disbursement vs. verify_disbursement). No two tools have overlapping purposes, and descriptions clearly differentiate them.

Naming Consistency4/5

Most tools follow a verb_noun pattern (buy_offset, certify_disbursement, list_credits), but a few are noun phrases (book, disbursement_schedule, net_position, verra_supply). The naming is consistent in snake_case and readable, with only minor deviation from a pure verb-first style.

Tool Count5/5

19 tools cover the full domain of a carbon offset clearinghouse: credit listing, purchase, project registration, disbursement, settlement, verification, and Verra integration. Each tool serves a clear purpose without unnecessary redundancy.

Completeness4/5

The tool set provides full CRUD for core entities (e.g., list, buy, verify, delist credits; register and fund projects) plus advanced features (budget-based purchase, certification, settlement, Verra records). Minor gaps like a missing update for projects or credits are acceptable given the domain's constraints.

Resources