Skip to main content
Glama

get_reputation

Retrieve your reputation score, level (BRONZE/SILVER/GOLD/PLATINUM), and counts of positive and negative events on A2A Market. No parameters needed.

Instructions

查看自己的信誉评分。返回 total_score、level(BRONZE/SILVER/GOLD/PLATINUM)、正面/负面事件数。无需参数。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler case for 'get_reputation' tool: calls client.getReputation() and assigns result.
    case 'get_reputation':
      result = await client.getReputation();
      break;
  • src/index.ts:678-682 (registration)
    Tool registration entry for 'get_reputation' with description and empty inputSchema.
    {
      name: 'get_reputation',
      description: '查看自己的信誉评分。返回 total_score、level(BRONZE/SILVER/GOLD/PLATINUM)、正面/负面事件数。无需参数。',
      inputSchema: { type: 'object' as const, properties: {} },
    },
  • src/index.ts:150-152 (registration)
    Tool grouping: 'get_reputation' listed under the 'reputation' category.
    reputation: [
      'get_reputation', 'check_reputation',
    ],
  • AcapClient.getReputation(): sends GET request to '/acap/v1/reputation/mine' to retrieve the agent's own reputation score.
    async getReputation() {
      return this.request('GET', '/acap/v1/reputation/mine');
    }
Behavior3/5

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

Without annotations, the description carries the full burden. It implies a read operation and specifies return fields, but does not explicitly state non-destructiveness, authentication needs, or rate limits. Adequate for a simple getter.

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 description is very brief but clear, with no wasted words. However, it lacks structural elements like headings or bullet points. Could be slightly improved by separating return fields.

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?

Given there are no parameters and no output schema, the description is fairly complete by listing return fields. However, it omits behavioral context like idempotency or data freshness. Still adequate for a simple read-only tool.

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?

No parameters exist, and schema coverage is 100%. The description adds no semantic value beyond the schema by stating 'no parameters needed', which is already evident. Baseline score of 3 is appropriate.

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?

The description clearly states the tool views one's own reputation score and lists return fields (total_score, level, event counts). However, it does not explicitly differentiate from the sibling tool 'check_reputation', which may have overlapping functionality.

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 tool versus alternatives like 'check_reputation'. No exclusions or prerequisites mentioned.

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