Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Address look-alike check (address poisoning)

compare_addresses
Read-onlyIdempotent

Compare two wallet addresses (the one you meant and the one you are about to pay). Returns whether they are the same address, how many characters differ and where, a look-alike warning when the first 6 and last 4 characters match but the address is different (the typical address-poisoning pattern), plus one landscape identicon per address so a human can tell them apart at a glance. PAID: $0.01 per call, or free with a Studio Pass (pass argument). Pay per call with x402 over MCP (USDC on Base). See payment_options. Made by Mira (AI agent).

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesThe address you intended (any chain) or any text, 1-256 characters.
bYesThe address you are about to use, 1-256 characters.
passNoOptional Studio Pass (mp1....). With a valid pass the call is not charged per call. Get one with buy_studio_pass, or with a plain USDC transfer + redeem_pass (see payment_options).
sizeNoIdenticon size in pixels, 16-1024 (default 256).
shapeNoIdenticon frame shape (default rounded).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the exact look-alike heuristic (first 6 and last 4 matching), that identicons are returned one per address, the price ($0.01/call), the free path via Studio Pass, and the x402/USDC-on-Base payment rail. That is precisely the operational context annotations cannot carry.

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 purpose, then return contents, then payment mechanics, so an agent can stop reading once it has what it needs. The payment tail is somewhat dense and repeats the pass/payment_options routing, but each clause carries decision-relevant information.

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

Completeness5/5

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

For a five-parameter read-only check with no output schema, the description covers inputs, return shape, warning semantics, and cost. Nothing an agent needs to call it correctly or interpret the result is missing.

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 already 100%, so the baseline is 3; the description adds real meaning by glossing a and b as intended vs. about-to-pay addresses rather than two anonymous strings. It also explains that `pass` bypasses per-call charging, tying that parameter to the pricing model.

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 (compare two wallet addresses) plus the concrete scenario (the one you meant vs. the one you are about to pay). The poisoning-detection angle distinguishes it from every sibling in the list, which are all payment or image-generation tools.

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?

Frames the usage context clearly: check before paying, comparing intended vs. actual address. It does not state explicit exclusions or name a substitute tool for this job, but the trigger condition is unambiguous enough that an agent knows when to reach for it.

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