Skip to main content
Glama
Sign In

VergeCommon

by io.github.jdhart81
OverviewDiscussionsAdmin

example_pooling_draft

Read-onlyIdempotent

Use when a person asks how pooling and benefit sharing work in a conservation co-op, or when you need a valid starting scenario for prepare_pooling_draft. Do not use it for real figures, prices or eligibility: every member, quantity and amount is synthetic. Takes no input. Returns a fictional three-member scenario and its modeled result (ecological reserve, sale, stewardship and treasury shares and each member's allocation in cents), with status flags showing nothing was executed, verified, issued or paid, plus a source receipt and the vergecommon.com calculator page.

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": "example_pooling_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds substantive context beyond them: all data is synthetic, and status flags show nothing was executed, verified, issued or paid, which prevents an agent from misreporting the result as real. It stops short of describing size, latency or failure modes, so it is not a full 5.

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 use case is front-loaded and the 'do not use it for real figures' caveat follows immediately, which is the right order. It is one dense paragraph, though — the return-value sentence packs shares, allocation units, status flags, receipt and URL together and would scan faster as a short list.

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

Completeness5/5

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

With no output schema, the description carries the return-shape burden and does so: it names the modeled outputs (ecological reserve, sale, stewardship and treasury shares, per-member allocation in cents), the status flags, the source receipt and the calculator page. Nothing an agent needs before calling is missing.

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?

There are zero parameters, which sets a baseline of 4, and the description confirms 'Takes no input', so an agent will not hunt for hidden arguments. There is nothing further to disambiguate.

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 specific verb and resource: it returns a fictional three-member pooling/benefit-sharing scenario and its modeled result, and it explicitly positions itself against the sibling prepare_pooling_draft. An agent can distinguish this sandbox/example tool from the real drafting tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use (a person asks how pooling and benefit sharing work, or you need a valid starting scenario for prepare_pooling_draft) and an explicit when-not-to-use (not for real figures, prices or eligibility), plus names the downstream alternative. That is the full when/when-not/alternative triad.

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

All VergeCommon 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