Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

offsets__settlement_batch

Summarize cash-settlement amounts for a buyer's carbon offset retirements, optionally filtered from a given timestamp.

Instructions

[offsets — verified-credit carbon offset clearinghouse] Read-only cash-settlement summary for a buyer: the list + exact sums (purchases, mass_g, cost_minor) of their retirements, optionally since an ISO-8601 timestamp — the statement a human settles in one transfer.

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": {
      "buyer": "<buyer>"
    },
    "name": "offsets__settlement_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.12
  2. Removedv0.1.11
  3. Changed3 schema fields changedv0.1.9
    • removedInput schema / properties / buyer / title
      Removed value: -"Buyer"
    • removedInput schema / properties / since / title
      Removed value: -"Since"
    • removedInput schema / title
      Removed value: -"settlement_batchArguments"
  4. Changed3 schema fields changed
    • addedInput schema / properties / buyer / title
      Added value: +"Buyer"
    • addedInput schema / properties / since / title
      Added value: +"Since"
    • addedInput schema / title
      Added value: +"settlement_batchArguments"
  5. Changed3 schema fields changed
    • removedInput schema / properties / buyer / title
      Removed value: -"Buyer"
    • removedInput schema / properties / since / title
      Removed value: -"Since"
    • removedInput schema / title
      Removed value: -"settlement_batchArguments"
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description explicitly labels the tool as read-only, which is the primary behavioral trait. It also lists the returned data fields (purchases, mass_g, cost_minor), adding transparency beyond the schema. However, it does not mention error conditions or rate limits, but since there are no annotations, this is acceptable.

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?

The description is extremely concise: two sentences covering purpose, data returned, and optional filtering. Every word adds value, and the most important information is front-loaded.

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 tool with two parameters and no output schema, the description explains the core functionality and output fields. However, it lacks details on the output format or how this tool fits into the offsets workflow, which would aid completeness.

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

Parameters3/5

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

The description adds meaning to the 'since' parameter by specifying it is an optional ISO-8601 timestamp. However, it does not explain the 'buyer' parameter format or constraints, which is a gap given the schema has 0% description coverage.

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 the tool provides a read-only cash-settlement summary for a buyer, listing exact sums of retirements. It distinguishes itself from other offsets tools by specifying that it returns aggregated settlement data, not individual purchases or lists.

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?

The description mentions it is read-only and optionally filterable by ISO-8601 timestamp, but does not explicitly state when to use this tool versus other offsets tools like 'offsets__net_position' or 'offsets__book'. No prerequisites or alternatives are provided.

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

Deploy Server

Other Tools