Skip to main content
Glama

Agent reputation

soma_reputation
Read-onlyIdempotent

Agent reputation from facts: signed receipts, violations and the running score.

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": "<agent>"
    },
    "name": "soma_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. What the description adds beyond that is provenance: the returned reputation is derived from signed receipts and violations and includes a running score, which tells the agent the result is computed rather than stored. It does not say whether the call fails for unknown agents or whether the score is cached/stale.

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?

One short sentence with no filler, and the payload (what the reputation is built from) is front-loaded. The colon-list structure is compact, though 'from facts' is vague enough that the sentence reads as a fragment rather than a full statement of behavior.

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?

An output schema exists, so return-value shape need not be spelled out, and annotations cover the safety profile. What remains missing for a one-param lookup is the identity format of 'agent' and the behavior for agents with no recorded facts — gaps an agent would hit on the very first call.

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

Parameters2/5

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

The single required parameter is named 'agent' with a 0% schema description coverage, so the schema gives no hint whether this is an agent ID, a registered name, or a public key. The description never mentions the parameter at all, so it fails to compensate for the coverage gap on the one input that matters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (an agent's reputation) and enumerates what feeds it — signed receipts, violations, a running score — which is more specific than the title alone. However, it is a noun phrase with no verb, so an agent must infer that this is a read/retrieval operation rather than, say, a reputation-update or recomputation call, and nothing distinguishes it from siblings like soma_verify or soma_stats.

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 named alternative. Given siblings such as soma_verify (which plausibly also touches signed receipts) and soma_stats, the description leaves the agent to guess whether reputation should be fetched here or composed from those tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources