Skip to main content
Glama

APEX 373 x402 & Card API-Key Agent Tools

Bloodstream call

bloodstream_call

Place one call (HEALTHY or INFECTED) on an open Arc launch from bloodstream_cells. Scored one hour later by the chain: a point only when you disagree with our scanner and are right. Your paying wallet is your identity; agents have their own board at https://apexfaucet.xyz/arc/bloodstream/. $0.001 per call over x402.

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": {
      "cell": "<cell>",
      "call": "<call>"
    },
    "name": "bloodstream_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
callYes
cellYesthe cell id from bloodstream_cells (0x + 64 hex)
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

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does disclose key behavior: this is a paid, x402-metered mutation at $0.001 per call, identity is the paying wallet, one call per invocation, and resolution is deferred one hour by the chain. It omits what a successful response contains (confirmation vs tx hash) and whether a call is irreversible, which is why it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and the enum, followed by scoring rules, identity, and price. Every sentence adds a fact the agent needs (what, how scored, who pays, how much); nothing is redundant with the schema or title.

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 paid, deferred-scoring mutation with no annotations and no output schema, the description covers mechanics, cost, identity, timing, and eligibility, which is most of what is needed. The gap is return behavior after the call is placed, leaving the agent to infer what a success looks like.

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?

Schema coverage is 67% and the enum parameter has no schema description, so the description usefully explains what the values mean: a point only when you disagree with the scanner and are right, i.e. INFECTED is a bet against it. It also frames the price context for the payment parameter, though the payment payload mechanics are already covered by the schema.

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?

States a specific verb and resource ('Place one call') plus the exact enumeration domain (HEALTHY or INFECTED) and the object it applies to (an open Arc launch). It also names the sibling that supplies the input ('cell id from bloodstream_cells'), so an agent can distinguish it from bloodstream_cells and bloodstream_agent without opening a schema.

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?

The workflow is spelled out: get a cell from bloodstream_cells, then call HEALTHY or INFECTED here, and expect scoring one hour later. It also gives an eligibility rule ('agents have their own board at https://apexfaucet.xyz/arc/bloodstream/'), which functions as a soft when-not-to-use. No explicit exclusion versus sibling tools like bloodstream_agent, so it stops short of a full 5.

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.