Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Default fund get

default_fund_get
Read-onlyIdempotent

Read the public statement of Bitroad's member loss-absorption fund: per currency (gbp, usd, eur), balance_minor, contributions_minor (net of contributions reversed with a refunded fee), draws_minor and draw_count, plus contribution_rate_bps (the share of each cleared job's platform fee credited to the fund) and as_of. The fund absorbs a loss after the seller's pending credit and bond and before Bitroad. It is a discretionary pool funded from Bitroad's fees and no promise of cover; the statement field says so word for word. Works without credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, the description explains the fund's role in loss absorption, its position after the seller's pending credit and bond and before Bitroad, that it is discretionary, and that there is no promise of cover. It also discloses that no credentials are needed, adding meaningful 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 front-loaded with the resource and returned fields, then adds relevant caveats about the fund's discretionary nature. It is dense but mostly earns its length; the phrase 'the statement field says so word for word' is slightly redundant but reinforces the no-promise caveat.

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 burden of explaining return values, and it does so thoroughly: currencies, balance_minor, contributions_minor, draws_minor, draw_count, contribution_rate_bps, and as_of. It also supplies enough domain context for an agent to interpret the statement correctly.

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?

The tool takes zero parameters, so there is no parameter semantics to clarify. The description instead spends its space defining returned fields and their meaning, which is appropriate for a no-argument read tool.

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 opens with a specific verb and resource: 'Read the public statement of Bitroad's member loss-absorption fund.' It then enumerates the exact fields returned per currency, making the tool's scope unmistakable and distinguishable from sibling get/list tools.

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?

It gives a clear usage context by stating the tool reads the public fund statement and explicitly notes that it 'Works without credentials.' It does not name alternatives or exclusions, but the use case is narrow and unambiguous.

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

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