Skip to main content
Glama

Arc antibody

arc_antibody

The on-chain immune attestation of an Arc token (ImmuneAttestations on Arc mainnet): grade A/B healthy, C watch, D sick, F infected, ? unproven, the sha256 evidence hash and the block it was written in. Read it before you buy: a public chain record, not a fresh check (a fresh one is arc_immune). attested:false means nobody bought a deep check of that token yet, which is not a clean bill of health. $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": {
      "token": "<token>"
    },
    "name": "arc_antibody"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesthe Arc token contract address (0x...)
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.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden and does well: it discloses that this is a public chain record rather than a live verification, explains the attested:false semantics, and states the cost ($0.001 per call over x402) plus the payment path. It doesn't cover failure modes (e.g., unknown token, insufficient/failed payment), which keeps it short of 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.

Conciseness4/5

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

Front-loads what the tool returns and packs a lot of useful information into a few sentences, but the grade enumeration and mid-sentence asides make it dense and slightly hard to scan. No sentence is wasted, though.

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?

With no output schema and no annotations, the description effectively documents the return shape (grade, evidence hash, block) and the attested flag. What remains thin is error/payment-failure behavior for a paid tool, which an agent would want before calling.

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 100%, so the parameters are already documented; the description still adds meaning by attaching the $0.001 x402 price to the payment parameter, clarifying why and how that field is used beyond the schema's mechanics. The token parameter gains only restatement.

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 (reads the on-chain immune attestation of an Arc token), enumerates the exact payload (grade A/B/C/D/F/?, sha256 evidence hash, block written in), and distinguishes itself from the sibling arc_immune by being a stored record rather than a fresh check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('Read it before you buy'), names the alternative (arc_immune for a fresh check), and adds an important caveat about interpretation: attested:false means nobody bought a deep check yet, not a clean bill of health.

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