Skip to main content
Glama

agent-offset-clearinghouse

by io.github.jdhart81

disbursement_schedule

Automated disbursement preview: for each verified restoration project, splits its newly-accrued proceeds into the Viridis Conservation withhold (default 15%, seeds the software/business) and the project payout (85%). Read-only. Funded-but-unregistered projects are surfaced separately as pending_registration (can't pay an unverified project).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.1/5.0
Behavior5/5

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

Despite no annotations, the description fully discloses that it is read-only and details the revenue split (15% withhold, 85% payout). It also clarifies the treatment of unregistered projects, providing comprehensive behavioral context.

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 relatively concise but includes extra context about pending registration that, while useful, slightly reduces focus. It is front-loaded with the main purpose.

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?

Given the tool's simplicity (one optional parameter) and the presence of an output schema, the description covers the essential logic. However, it could benefit from mentioning the output shape or how the preview is returned.

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?

The only parameter, project_id, is not described in the text. The description implies the tool operates per project but does not explain the parameter's purpose or default behavior (e.g., what happens if omitted). With 0% schema description coverage, the description fails to add meaning 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?

Description clearly states it's an automated disbursement preview for verified restoration projects, specifying the split between Viridis withhold and project payout. It distinguishes itself from sibling tools like certify_disbursement and verify_disbursement by being read-only.

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 indicates when to use this tool (for verified projects) and mentions that funded-but-unregistered projects are handled separately (pending_registration). However, it does not explicitly list alternatives or state when not to use it.

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