Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Panel list open

panel_list_open
Read-onlyIdempotent

Member panel: list open dispute cases you may sit on. A case is a service dispute the acceptance engine and any verifier could not settle; a quorum of 3 members decides it by majority, release (the seller is paid) or refund (the buyer is refunded in full). Lists nothing (member: false) until you qualify to sit, and never a job you bought, fulfilled or verified. Each case is blind to the parties: the job's scope, output schema and acceptance block, the deliverable, the buyer's reason and the seller's response, with no ids, names or stores. Each carries its deadline and the fee_pence it pays, split across the counted votes.

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": {
      "limit": "<limit>"
    },
    "name": "panel_list_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesMost cases to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior. The description adds substantive context beyond those annotations: membership gating, exclusion of your own jobs, blind-to-parties returned fields with no ids/names/stores, and the deadline and fee split. This is rich, specific and consistent with the annotations.

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 leading sentence front-loads the core action and scope, and subsequent details are relevant to understanding the listing. The remaining material is dense and delivered in one long paragraph, which could be easier to scan, but no sentence is clearly wasted.

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?

For a complex panel-dispute listing tool with no output schema, the description supplies the missing return semantics (blind fields, deadline, fee_pence), the membership gating rule and the exclusion rule. The single input parameter is fully covered by the schema, so nothing critical for correct invocation is omitted.

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?

Schema description coverage is 100% for the single limit parameter, so the schema already explains 'Most cases to return.' The description adds no parameter-specific syntax, default behavior or filtering semantics beyond what the schema provides, so the baseline applies.

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?

Starts with a specific verb and resource ('list open dispute cases') and scopes the result to member panel cases you may sit on, while defining what a case is. The 'open' list framing and member qualification distinguish it from general dispute lookups and from the singular detailed case 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?

States the qualification condition (member: false lists nothing until you qualify) and explicit exclusions (never jobs you bought, fulfilled or verified), which tells the agent when the tool returns data. It does not name follow-on alternatives such as panel_get_case or panel_vote, so it stops short of full when/when-not/alternative guidance.

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