Skip to main content
Glama

moltguard_score

Read-only

Generate a 0–100 trust score for a Base wallet address by analyzing on-chain activity, ERC-8004 registration, USDC balance, counterparty diversity, and MolTrust credentials.

Instructions

Get an agent trust score for a Base wallet address.

Analyzes on-chain activity, ERC-8004 registration, USDC balance, counterparty diversity, and MolTrust credentials to produce a 0-100 score.

Args: address: Base (EVM) wallet address (0x...)

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

Input Schema

NameRequiredDescriptionDefault
addressYesBase (EVM) wallet address (0x...)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / address / description
      Added value: +"Base (EVM) wallet address (0x...)"
  2. First observedv1.2.0

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a non-mutating read, so the description earns credit for the extra context it supplies: the five data sources consulted and the 0-100 output scale, which is genuinely useful for interpreting results. It stops short of saying whether the score is computed live or cached, how long it takes, or what happens for an address with no history or on a non-Base chain.

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 purpose and method are front-loaded in two tight sentences and the 0-100 range is stated up front. The trailing Args block is pure duplication of the schema and could be dropped, but the overall size is appropriate.

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?

An output schema exists, so return values need not be spelled out, and the description still volunteers the score range. For a single-parameter, read-only scoring tool, everything an agent needs to decide and call correctly is present; only error and freshness behavior remain unstated, which is minor.

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 parameter is fully described in the schema, so the baseline applies. The description's Args block simply restates the schema text ('Base (EVM) wallet address (0x...)') without adding format details such as checksum requirements, chain-ID expectations, or behavior for malformed addresses.

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 ('Get an agent trust score for a Base wallet address') and enumerates the signals that feed the score (on-chain activity, ERC-8004 registration, USDC balance, counterparty diversity, MolTrust credentials) plus the output range. It is clear what the tool does, but it never differentiates itself from the similarly named sibling mt_get_trust_score, leaving the agent to guess which scorer to call.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no exclusions or named alternatives. The presence of a close sibling (mt_get_trust_score) makes the absence of routing guidance a real gap rather than a minor one.

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