Skip to main content
Glama

Bot safety

bot_safety

Combined bot preflight safety screen on Base or Solana ($0.005): pass domain, payee, chain/amount/from/to/data/raw, or signer/tx for SAFE, CAUTION, RISKY, or INCOMPLETE. $0.005 per call over x402 (USDC on Base or USDC on Solana only). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
toNotarget contract/recipient
txNotx hash/payload
rawNoraw tx hex/base64
dataNocalldata hex
fromNosender address
chainNobase or solana
payeeNorecipient address
amountNotransfer amount
domainNophishing/domain check target
signerNoSolana signer
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 burden and does well: it discloses cost ($0.005 per call), accepted payment rails (USDC on Base or Solana only), and the two-phase x402 handshake with its failure-adjacent INCOMPLETE verdict. It does not cover what happens on payment rejection, insufficient funds, or what the response payload contains, which keeps it from 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-loaded with the capability, then inputs, then outputs, then pricing and payment flow — a sensible order. The $0.005 figure appears twice and the second sentence partially restates the first, costing a small amount of density.

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 an 11-parameter, zero-annotation, no-output-schema tool, the description covers purpose, verdict vocabulary, cost, payment mechanism, and call sequence. What is missing is guidance on minimum viable parameter combinations and the shape of a returned result, which matters given every parameter is optional.

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%, so the baseline is 3. The description does add genuine grouping meaning by implying two input modes (domain/payee/chain/amount/from/to/data/raw versus signer/tx), but it does not explain which combinations are required for a valid screen, leaving the agent to infer from the schema prose alone.

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 ("Combined bot preflight safety screen on Base or Solana") and enumerates the exact result classes it emits (SAFE, CAUTION, RISKY, INCOMPLETE). An agent knows immediately this is a risk-scoring check for a proposed bot transaction, not a general query tool.

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?

Gives a clear usage sequence: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. It also frames the context as a preflight check. It stops short of stating when-not to use it or naming an alternative screening tool, so it is clear but not fully routing.

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