Skip to main content
Glama

ChainGuard Web3 & MCP Shield

check_tx_firewall

Pre-flight EVM transaction drainer & unlimited approval firewall (Base/Arbitrum/Polygon).

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": {
      "to": "<to>"
    },
    "name": "check_tx_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
networkNobase
calldataNo0x

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real substance beyond the schema: the threat models screened for and the three supported networks. However, it never states whether the call is purely read-only/dry-run, whether it simulates execution, or how a positive finding versus a clean result is represented.

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?

A single front-loaded line with no filler; the core purpose leads and the chain scope trails. It is efficient, though so compressed that it omits information the agent actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a security-critical tool with no annotations, no output schema, and zero schema description coverage, this description is too thin. An agent cannot learn what the response looks like, how to interpret a flagged transaction, or what to do with the result, which matters greatly for a firewall tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with three parameters, so the description must compensate and largely does not. The parenthetical 'Base/Arbitrum/Polygon' partially documents the 'network' parameter's accepted values, but 'to' and especially 'calldata' receive no explanation of expected format (e.g., hex encoding, empty-calldata semantics for plain transfers).

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 names a specific check operation and two concrete risk classes it screens for (drainers and unlimited approvals), plus the supported EVM chains. The verb is only implied by 'Pre-flight ... firewall' rather than stated outright, but an agent can tell this is a pre-signing transaction safety check and not a delegation or token-program check like the siblings.

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?

'Pre-flight' implies the moment of use (before signing or broadcasting a transaction), but the description never states that explicitly and gives no when-not conditions or alternatives. The chain list hints at scope selection but is not framed as routing guidance.

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