Skip to main content
Glama

Screen address

screen_address

Screen an Ethereum address or .eth ENS name for on-chain reputation risk. Costs 1 credit. Returns a signed reputation score (-100 to +100), a risk band, a confidence level, a sanctioned flag, the top evidence factors, a screeningId, and a link to the full report. The enhanced review is generated in the background. Fetch it with get_screening_narrative(screeningId). Use the score, band, and sanctioned flag to gate pre-trade or payout flows.

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

Input Schema

NameRequiredDescriptionDefault
addressYesEthereum address (0x...) or `.eth` ENS name (e.g. vitalik.eth) to screen. ENS names resolve to their current mainnet address and must resolve or the call errors. Addresses are case-insensitive and need not be checksummed.

Output Schema

NameRequiredDescriptionDefault
bandYesReputation band, e.g. Low Risk, Reputable
scoreYesSigned reputation score from -100 to +100. Lower is worse.
addressYesThe screened address
summaryYesOne line verdict headline
bandCodeYesBand identifier, e.g. LOW_RISK, REPUTABLE
evidenceYesUp to 10 signals behind the verdict, most severe first
reportUrlYesLink to the full report on the Probity dashboard
confidenceYesEngine confidence in the result
sanctionedYesTrue if the address is a direct OFAC match
screenedAtYesWhen the screen ran (ISO-8601)
screeningIdYesImmutable identifier for this screen (rsr_...)
transactionCountYesNumber of transactions analysed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / transactionCount / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / transactionCount / minimum
      Added value: +-9007199254740991
  2. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"Ethereum address (0x...) or `.eth` ENS name (e.g. vitalik.eth) to screen"New value: +"Ethereum address (0x...) or `.eth` ENS name (e.g. vitalik.eth) to screen. ENS names resolve to their current mainnet address and must resolve or the call errors. Addresses are case-insensitive and need not be checksummed."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: it costs 1 credit (which explains readOnlyHint=false despite returning data), the score is signed, and the enhanced review is produced asynchronously in the background and must be fetched separately. It does not address failure modes, whether a repeat call re-charges, or latency, which keeps it short of 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?

Purpose and cost are front-loaded in the first two sentences, and the gating use case closes the description. The enumerated return-value list partially duplicates the output schema and could be trimmed, but the remaining sentences are functional.

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?

Covers cost, the credit implication of a non-read-only call, the async narrative handoff, and the decision-relevant outputs for a gating flow. With an output schema present it need not have described return fields at all, so nothing an agent needs before calling is missing.

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% and the single `address` parameter is fully documented in the schema, including ENS resolution and case-insensitivity. The description only restates the accepted input types, adding no semantics the schema lacks, so the baseline 3 applies.

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 ('Screen an Ethereum address or `.eth` ENS name') plus the object of the screening ('on-chain reputation risk'). It also names the sibling it hands off to (get_screening_narrative) for the background review, so an agent can distinguish it from the history/comparison siblings without opening schemas.

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 an explicit application context: 'Use the score, band, and sanctioned flag to gate pre-trade or payout flows,' and names the follow-up call. It does not say when to skip screening (e.g., reuse get_address_screening_history instead of paying another credit), so an agent has no explicit exclusion rule for the most likely redundant call.

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