Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

erc8004_get_reputation

Retrieve ERC-8004 agent reputation data including score, count, and decimals. Filter by optional tags to analyze on-chain agent performance metrics.

Instructions

Get ERC-8004 agent reputation summary (score, count, decimals).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesOn-chain agent ID (uint256)
tag1NoOptional tag1 filter
tag2NoOptional tag2 filter

Implementation Reference

  • packages/mcp/src/tools/erc8004-get-reputation.ts:19-27 (handler)
    Handler function that executes the API request for the erc8004_get_reputation tool.
      async (args) => {
    const params = new URLSearchParams();
    if (args.tag1) params.set('tag1', args.tag1);
    if (args.tag2) params.set('tag2', args.tag2);
    const qs = params.toString();
    const result = await apiClient.get(`/v1/erc8004/agent/${args.agent_id}/reputation${qs ? `?${qs}` : ''}`);
    return toToolResult(result);
  },
);
  • packages/mcp/src/tools/erc8004-get-reputation.ts:14-18 (schema)
    Zod schema defining the input arguments for the tool.
    {
  agent_id: z.string().describe('On-chain agent ID (uint256)'),
  tag1: z.string().optional().describe('Optional tag1 filter'),
  tag2: z.string().optional().describe('Optional tag2 filter'),
},
  • packages/mcp/src/tools/erc8004-get-reputation.ts:10-28 (registration)
    Registration function that defines the tool in the MCP server.
    export function registerErc8004GetReputation(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
  server.tool(
    'erc8004_get_reputation',
    withWalletPrefix('Get ERC-8004 agent reputation summary (score, count, decimals).', walletContext?.walletName),
    {
      agent_id: z.string().describe('On-chain agent ID (uint256)'),
      tag1: z.string().optional().describe('Optional tag1 filter'),
      tag2: z.string().optional().describe('Optional tag2 filter'),
    },
    async (args) => {
      const params = new URLSearchParams();
      if (args.tag1) params.set('tag1', args.tag1);
      if (args.tag2) params.set('tag2', args.tag2);
      const qs = params.toString();
      const result = await apiClient.get(`/v1/erc8004/agent/${args.agent_id}/reputation${qs ? `?${qs}` : ''}`);
      return toToolResult(result);
    },
  );
}

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Discloses return payload structure (score, count, decimals) compensating for missing output schema. However, with zero annotations, description fails to disclose critical operational traits: read-only nature, gas costs, error handling for invalid agent_ids, or whether this queries on-chain vs. indexed data.

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?

Single efficient sentence front-loaded with action and resource. Parenthetical return value list maximizes information density with zero redundancy.

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?

Adequate for a 3-parameter read tool: mentions return fields compensating for no output schema. However, lacks explicit read-only declaration or blockchain-specific context (e.g., 'view function') expected given no annotations.

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 has 100% description coverage documenting all three parameters (agent_id, tag1, tag2). Description adds no parameter-specific syntax guidance but implies tag filters affect the summary; baseline 3 appropriate given schema completeness.

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?

Clear verb ('Get') and resource ('ERC-8004 agent reputation summary') with specific return fields (score, count, decimals). However, lacks explicit differentiation from sibling 'erc8004_get_agent_info' which may overlap in scope.

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?

No guidance on when to use this vs. alternatives (e.g., erc8004_get_agent_info), when to apply tag1/tag2 filters, or prerequisites like agent existence checks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server