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

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

offsets__book

Access the full carbon offset credit book with per-credit details and book-wide mass conservation totals for verified credits.

Instructions

[offsets — verified-credit carbon offset clearinghouse] The full credit book with per-credit and book-wide mass conservation totals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "offsets__book"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"bookArguments"
  2. Changed2 schema fields changedv0.1.9
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"bookArguments"
  3. Changed2 schema fields changed
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"bookArguments"
  4. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"bookArguments"
  5. First observed

TDQS

A3.7/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only mentions the output (credit book with totals) but lacks details on read-only nature, side effects, or prerequisites.

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 short and to the point, though the bracketed prefix is somewhat extraneous. It conveys the core purpose efficiently.

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 zero-parameter read tool, the description adequately explains the output (full credit book with totals). No output schema exists, but the description suffices.

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?

No parameters exist (0 params), so baseline is 4. The description adds no parameter info, but none is needed.

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 it provides 'the full credit book with per-credit and book-wide mass conservation totals,' distinguishing it from sibling tools like offsets__list_credit or offsets__net_position.

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 implies usage for retrieving the full credit book but provides no explicit guidance on when to use it vs. alternatives or 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.

Deploy Server

Other Tools