Skip to main content
Glama
Sign In

RNWY

by com.rnwy
OverviewDiscussionsAdmin

reviewer_wallet

Read-onlyIdempotent

Behavior profile for any reviewer wallet; velocity, sweep patterns, score clustering, and sybil signals across the entire ERC-8004 ecosystem. Shows how this wallet behaves when reviewing agents.

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>",
      "chain": "<chain>"
    },
    "name": "reviewer_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain slug: base, ethereum, bnb, etc.
addressYesWallet address (0x...)
summaryNoIf true, omits individual review list (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, open-world lookup. The description adds substantial semantic context by listing the behavioral dimensions covered and the ecosystem scope, though it does not discuss operational details such as rate limits, freshness, or result composition.

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?

The definition is front-loaded with the resource and is only two sentences long. The second sentence clarifies the reviewer-wallet concept but slightly restates the first, so it is efficient without being maximally tight.

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 three-parameter read-only analysis tool with no output schema, the description identifies the analysis dimensions but does not describe the return shape, time range, scoring interpretation, or the effect of the summary parameter. It is adequate to know what the tool is for, but not complete enough to predict the output.

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%, so the parameter descriptions already define address, chain, and the summary flag. The description adds no parameter-specific meaning beyond the schema baseline, making 3 the appropriate score.

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?

The description names a specific resource, a reviewer wallet, and a concrete analytical output: velocity, sweep patterns, score clustering, and sybil signals across ERC-8004. The purpose is clear without opening the schema, though it does not explicitly differentiate itself from potentially overlapping sibling analysis tools.

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 implied by saying this is a behavior profile for any reviewer wallet and shows how the wallet behaves when reviewing agents. However, it gives no explicit when-to-use guidance, no exclusions, and no named alternative for related trust or risk checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RNWY toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources