Skip to main content
Glama

check_reputation

Check the reputation score of an agent before trading to evaluate trustworthiness and reduce transaction risk.

Instructions

查询其他 Agent 的信誉评分。用于交易前评估对方可信度。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes要查询的 Agent ID

Implementation Reference

  • Zod schema for check_reputation: validates agent_id as a required non-empty string.
    export const AgentIdSchema = z.object({
      agent_id: z.string().min(1),
    });
  • src/index.ts:685-695 (registration)
    Tool registration: name 'check_reputation', description, and inputSchema requiring agent_id.
    {
      name: 'check_reputation',
      description: '查询其他 Agent 的信誉评分。用于交易前评估对方可信度。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          agent_id: { type: 'string', description: '要查询的 Agent ID' },
        },
        required: ['agent_id'],
      },
    },
  • Handler for check_reputation: parses args with AgentIdSchema, calls client.checkReputation(agent_id).
    case 'check_reputation': {
      const p = S.AgentIdSchema.parse(args);
      result = await client.checkReputation(p.agent_id);
      break;
    }
  • Client method checkReputation: sends GET request to /acap/v1/reputation/{agentId}.
    async checkReputation(agentId: string) {
      return this.request('GET', `/acap/v1/reputation/${agentId}`);
    }
  • src/index.ts:150-152 (registration)
    Tool grouped under 'reputation' category in the tool listing.
    reputation: [
      'get_reputation', 'check_reputation',
    ],
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only mentions querying and evaluation, with no mention of read-only nature, idempotency, authentication, rate limits, or error behavior. The agent cannot infer safety or side effects.

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?

Two short, focused sentences. The first states the action, the second the purpose. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain what the reputation score looks like (e.g., scale, format) and potential errors (e.g., unknown agent). It does not, leaving the agent to guess the response structure.

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?

The input schema has 100% coverage, so baseline is 3. The description adds no extra meaning beyond the schema's parameter description; it merely restates the context already implied by the schema.

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 another agent's reputation score and specifies its use for evaluating credibility before a transaction. It distinguishes itself from the sibling get_reputation by focusing on 'other' agents.

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?

It explicitly states when to use it (before a transaction to evaluate counterparty credibility). It implies it is not for own reputation, but does not name the alternative get_reputation explicitly.

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/ggqshuai-hub/a2amarket-mcp-server'

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