Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_check_reputation

Read-onlyIdempotent

Retrieve an ERC-8004 registered agent's composite trust score (0-100), letter grade (A-F), historical clearing count, and Sybil wash-trading penalty flags by numeric agentId. Returns arbiter-signed reputation metrics and sybilFlags. Use this ONLY for registered ERC-8004 agent IDs (e.g. '124595'); for raw 0x wallet address OFAC/balance profiling use nullclear_score_wallet, and for legal corporate liability limits use nullclear_verify_mandate.

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": {
      "agentId": "<agentId>"
    },
    "name": "nullclear_check_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesRegistered numeric ERC-8004 agent token ID (e.g. '124595')
chainIdNoTarget EVM chain ID (8453 for Base Mainnet, 84532 for Base Sepolia)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), so the description's contribution is the provenance framing — metrics are 'arbiter-signed' — plus naming sybilFlags as a returned field, which is useful behavior an agent cannot see elsewhere given there is no output schema. It stops short of describing failure behavior for unregistered or non-existent agentIds, which is a real gap for an openWorld lookup.

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?

Three dense sentences with zero filler: capability and return payload first, then the input constraint, then sibling routing. The parenthetical return-field list earns its space precisely because no output schema exists.

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 simple two-parameter read tool with a fully described schema, the definition supplies capability, return contents, input constraint, and sibling routing — enough to call it correctly. The only material omission is what happens when the agentId is unregistered or unknown, which matters for an openWorld lookup.

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 with types, defaults, and an example, making 3 the baseline. The description reinforces that agentId must be a registered numeric ERC-8004 token ID rather than a 0x address, but chainId is not mentioned at all and no validation or error semantics are added.

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?

The description opens with a specific verb and resource — retrieve an ERC-8004 registered agent's composite trust score — and enumerates the concrete return fields (0-100 score, A-F grade, clearing count, Sybil flags). It also states the selector input (numeric agentId), so an agent can distinguish it from wallet-scoring and mandate-verification siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit inclusion criteria ('ONLY for registered ERC-8004 agent IDs') and names two alternatives with the conditions that select them: nullclear_score_wallet for raw 0x address OFAC/balance profiling and nullclear_verify_mandate for legal corporate liability limits. Both branches of the routing decision are covered.

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.