Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bitbrain_catalog

Browse a live catalog of P2P GPU inference swarm offerings to see which models are served, by whom, and at what trust level; use it to choose providers before paid inference.

Instructions

BitBrain - BitTorrent for LLMs. Live catalog of the P2P GPU inference swarm: which models are served, by whom, at what trust. Paid use: POST https://x402-agent-pay.com/bitbrain/infer with an X-Payment header (0.005 USDC via x402 on Base L2). Catalog is free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It explains that the catalog is free, what information it contains, and that paid inference is handled elsewhere via a specific x402 endpoint with a stated price and payment header. It does not explicitly state read-only behavior or return format, but for a catalog tool the behavioral picture is substantially clear.

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 front-loaded: it first explains the concept, then the catalog contents, then payment scope. The paid inference endpoint is somewhat tangential but still useful for clarifying what this tool does not do, and no sentence is wasted.

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 catalog tool with no output schema, the description gives enough context: what the catalog shows, that it is free, and how paid inference works separately. It could be slightly more explicit about the returned format, but the qualitative content description is sufficient for an agent to understand the tool's role.

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 has zero input parameters, so there is no parameter semantics to clarify beyond the schema. The description appropriately adds context about the catalog's purpose and the separate paid inference endpoint rather than inventing parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource: a live catalog of the P2P GPU inference swarm, listing which models are served, by whom, and at what trust. That is clear and distinctive, but it does not explicitly differentiate this tool from similarly named siblings such as data_catalog or marketplace_browse.

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 that this tool is for browsing the free catalog, while actual inference is a separate paid HTTP endpoint with an X-Payment header. It does not explicitly say when to choose this tool over sibling catalog or marketplace tools, so the guidance is present but only implied.

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