Skip to main content
Glama

MolTrust MCP Server

by io.github.MoltyCel
OverviewDiscussionsAdmin

moltrust_erc8004

Query the ERC-8004 on-chain agent registry on Base.

Resolve MolTrust agents to their on-chain ERC-8004 identity, fetch Agent Cards,
or look up on-chain agents by their agentId.

Args:
    action: One of "card", "resolve", or "well-known"
    did: Agent DID (required for "card", e.g. "did:moltrust:a1b2c3d4e5f60718")
    agent_id: On-chain ERC-8004 agent ID (required for "resolve", e.g. 21023)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
didNo
actionYes
agent_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It uses verbs like 'Query', 'Resolve', 'fetch', and 'look up' implying read-only behavior, but it never explicitly states that the tool is non-destructive or has no side effects. It also does not mention rate limits, costs, or the nature of the 'well-known' action, leaving some behavioral ambiguity.

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?

The description is concise and front-loaded: the main purpose is stated in the first sentence, followed by a clear action list and parameter details. Every sentence serves a purpose, with no wasted words or redundant explanations.

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?

The description covers the three actions and parameter requirements adequately, and the presence of an output schema (though not shown) reduces the need to describe return values. It omits details on the 'well-known' action and potential error conditions, but overall it gives an agent enough to invoke the tool correctly for the primary use cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully explain the parameters. It does this excellently: it lists the three valid action values, specifies which parameter is required for which action, and provides concrete examples for did and agent_id. This adds substantial meaning beyond the bare schema types and defaults.

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 clearly states the tool queries the ERC-8004 on-chain agent registry on Base, and enumerates three specific actions (card, resolve, well-known) with distinct resources. It differentiates from all sibling tools, none of which mention ERC-8004 or on-chain registry lookups.

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?

The description provides clear context by specifying which parameter is required for which action (e.g., did for 'card', agent_id for 'resolve'), giving the agent enough to decide when to call it. However, it does not explicitly name alternatives or state when not to use this tool, though the sibling set makes the niche obvious.

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

All MolTrust MCP Server 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