Skip to main content
Glama

Know Your Agent: trust-check a wallet

check_agent_wallet

Trust score and level for an AI-agent wallet (or any wallet) before you transact with it: signature-verified identity plus its on-chain track record in GL1TCH scans.

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": {
      "address": "<address>"
    },
    "name": "check_agent_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNosolana (default), ethereum, base, bsc, arbitrum, polygon, …
addressYesWallet or token address: a Solana base58 address or a 0x EVM address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the data sources behind the score (signature verification, on-chain history), which is genuine added context, but says nothing about whether the call is read-only, cost/rate limits, or what happens with unknown/unindexed wallets.

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 dense sentence that front-loads the return value and then the evidentiary basis. Nothing is wasteful, though the parenthetical '(or any wallet)' is slightly awkward and could be tightened.

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

Completeness3/5

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

For a two-parameter read tool this covers the essentials, but with no output schema the description should have hinted at the return shape — score range or what 'level' values exist — since interpreting the result is the whole point of the call.

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 both parameters are already documented, including chain options and address formats. The description adds only that the same call works for 'any wallet,' and says nothing about the chain parameter's default or multi-chain behavior beyond what the schema states.

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?

States a specific resource (an AI-agent wallet) and what it returns (a trust score and level), with the evidence basis named: signature-verified identity plus on-chain track record. It implicitly separates itself from siblings by saying 'wallet (or any wallet)' versus scan_token's token focus, but never names them explicitly.

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?

'Before you transact with it' gives a clear triggering context for the tool, so an agent knows this is pre-transaction due diligence. It stops short of naming alternatives or exclusions — there's no guidance on when to prefer deployer_reputation or scan_token instead.

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.