Skip to main content
Glama
io.github.ffnnkk/suuq-market-mcp

io.github.ffnnkk/suuq-market-mcp

by ffnnkk

get_agent_reputation

Read-only

Look up an agent's reputation score, transaction count, and verification status by agent ID to assess marketplace trust before transacting.

Instructions

Look up the reputation score, transaction count, and verification status of any agent.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the returned fields, which is useful since no output schema exists, but it says nothing about behavior for unknown or invalid agent IDs, score ranges, or freshness of the 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?

A single front-loaded sentence with no filler; the returned fields are packed in efficiently and nothing is redundant.

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?

For a simple one-parameter read tool with annotations covering safety and no output schema, stating the returned fields makes the definition largely self-sufficient. Only edge-case behavior (nonexistent agent) is left unstated.

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?

Only one parameter exists and the schema fully documents it as an agent UUID (100% coverage). The phrase 'any agent' loosely confirms arbitrary agent IDs are accepted, but no format or example detail is added beyond the schema.

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 names a specific verb (look up) and resource (an agent's reputation) and enumerates what is returned: reputation score, transaction count, verification status. That is clearly distinct from the sibling tools (listings, profile, transactions), though it never explicitly contrasts itself with them.

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 mention of alternatives such as get_my_profile for self-data. An agent can infer this is a read of another agent's trust signals, but the description supplies no selection criteria.

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