Skip to main content
Glama
Sign In

Aval

by cloud.hstgr.srv1024618.aval
OverviewDiscussionsAdmin

check_agent_trust

Trust score (0-100) of an AI agent before paying it. Counts only ERC-8004 reviews on Base that follow a real USDC payment from a wallet the agent did not fund. Input: 0x address or ERC-8004 agent id. Costs $0.01 in USDC on Base (x402).

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": {
      "agent": "<agent>"
    },
    "name": "check_agent_trust"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and adds meaningful context: score range, data source filtering (ERC-8004 reviews on Base tied to real USDC payments from wallets the agent did not fund), and a $0.01 x402 cost. It does not explicitly state read-only safety or failure modes, preventing 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose and methodology, then input and cost. No wasted words.

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?

Covers purpose, scoring methodology, input format, and cost, which is strong for a 1-param tool with no annotations or output schema. Missing only sibling differentiation and explicit usage guidance.

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 0% and the schema only defines a string, so the description adds essential meaning by specifying accepted input formats: a 0x address or ERC-8004 agent id. This compensates well for the bare schema.

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 verb and resource: checking an AI agent's trust score, with the 0-100 range. It does not differentiate from the sibling reputation_overview, so it falls short of a 5.

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?

Implies usage with 'before paying it', giving some context, but no explicit when-to-use, when-not, or alternative guidance. The sibling reputation_overview is not mentioned.

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

All Aval 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