Skip to main content
Glama

Bloodstream cells

bloodstream_cells

The live Bloodstream: every new Arc launch open for calls right now, with our scanner's call (HEALTHY / INFECTED / none), pool fee, hook, round-trip cost, cell id and seconds left. $0.001 per call over x402. Then call it with bloodstream_call.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the paid-model detail ($0.001 per call over x402) and enumerates the returned fields, which is real added context. However it says nothing about whether the listing itself is charged, freshness/caching of the live scan, or rate limits on repeated polls.

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?

Two tight sentences, front-loaded with the resource and its contents, then the cost model. The trailing 'Then call it with bloodstream_call' is slightly ambiguous in its pronoun and reads as an afterthought rather than a clean routing instruction.

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 and no annotations, the description compensates by listing exactly what comes back per cell and noting the payment cost. For a zero-required-parameter listing tool, an agent has enough to call it and interpret the response.

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 coverage is 100% for the single 'payment' parameter, and the schema already explains the signed x402 payload. The description adds only the price point relevant to that payment, which is marginally useful but does not add syntax or conditional meaning beyond the schema.

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?

States a specific resource and scope: live Arc launches open for calls right now, and enumerates what each cell carries (scanner verdict, pool fee, hook, round-trip cost, cell id, seconds left). An agent can tell this is a discovery/list tool, distinct from the sibling bloodstream_call which performs the call action.

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 closing 'Then call it with bloodstream_call' implies a discover-then-act workflow and implicitly routes to the sibling, but it is phrased as a sequence rather than an explicit when-to-use rule. There is no statement of when NOT to use it or what qualifies a cell worth calling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources