Skip to main content
Glama

Caelara Shield

shield_audit_token

Screen a token and/or an EVM transaction: token safety score, decoded transaction risks (unlimited approvals, failed or contract-creating transactions), address-poisoning lookalike check (0.050 USDC per 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": "shield_audit_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashNoEVM transaction hash (0x + 64 hex) to decode and screen
chainNobase|ethereum|arbitrum|optimism (default base)
tokenNoToken contract (0x...) or Solana mint to screen
destinationNoAddress you intend to pay
known_addressesNoAddresses you trust, to detect lookalike destinations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the entire behavioral burden. It does add real value by disclosing cost (0.050 USDC per call) and the specific checks performed, but it says nothing about what happens when zero parameters are supplied (all five are optional), whether results are combined into one response, or what the response looks like.

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?

A single dense sentence with the screening action front-loaded, the checked risk categories in the middle, and the price in a trailing parenthetical. Nothing is redundant and every clause conveys distinct information.

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 five-parameter, fully-optional screening tool with no output schema and no annotations, the description covers purpose, checks performed, and cost. The main residual gap is the semantics of an empty invocation and the shape of the result set, which matters somewhat given that nothing else documents it.

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 description coverage is 100%, so the schema already explains hash, chain, token, destination, and known_addresses individually, including the default chain of base. The description reinforces that the lookalike check ties destination to known_addresses, but adds no format, precedence, or combination semantics beyond the schema, so the baseline 3 applies.

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?

Uses a specific verb ("Screen") with two named resources (token and/or EVM transaction) and enumerates the concrete outputs: token safety score, decoded transaction risks such as unlimited approvals and contract-creating transactions, and an address-poisoning lookalike check. That makes it clearly distinct in kind from shield_proxy_fetch, shield_scan_prompt, and shield_validate_output, though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer this is a pre-interaction safety screening step, reinforced by the per-call price. There is no explicit when-to-use/when-not guidance, no statement about whether token and transaction screening should be done together or separately, and no mention of alternatives for the cases it doesn't cover.

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