Synthex Forge — x402 Paid Agent Services

Get Agent Reputation

get_agent_reputation

Read-onlyIdempotent

Reputation scored from dated, signed behaviour events rather than self-reported. use it rather than assess_agent_verdict for agent reputation, not agent verdict; an object with 34 fields including activity, agent.

Input Schema

Name	Required	Description	Default
`agent`	No	The identifier of the agent the operation concerns.
`events`	No	The events this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ts`	No	The `ts` field of the response.
`note`	No	A note on how the answer was produced.
`agent`	No	The `agent` field of the response.
`fails`	No	The `fails` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`events`	No	The `events` field of the response.
`sha256`	No	The `sha256` field of the response.
`framing`	No	The `framing` field of the response.
`metrics`	No	The `metrics` field of the response.
`outcome`	No	The `outcome` field of the response.
`verdict`	Yes	The decision this tool returned.
`activity`	No	The `activity` field of the response.
`disputes`	No	The `disputes` field of the response.
`evidence`	No	The `evidence` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`freshness`	No	The `freshness` field of the response.
`successes`	No	The `successes` field of the response.
`amount_usd`	No	The amount the operation concerned.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`success_rate`	No	The `success_rate` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`dispute_count`	No	The `dispute_count` field of the response.
`missingFields`	No	The `missingFields` field of the response.
`avg_amount_usd`	No	The `avg_amount_usd` field of the response.
`providedFields`	No	The `providedFields` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`figuresProvided`	No	The `figuresProvided` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`reputation_score`	No	The `reputation_score` field of the response.
`total_amount_usd`	No	The `total_amount_usd` field of the response.
`observed_outcomes`	No	The `observed_outcomes` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed36 schema fields changedOct 31, 2026

addedOutput schema / properties / activity

Added value: +{
+  "description": "The `activity` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / agent

Added value: +{
+  "description": "The `agent` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / amount_usd

Added value: +{
+  "description": "The amount the operation concerned.",
+  "type": "number"
+}

addedOutput schema / properties / avg_amount_usd

Added value: +{
+  "description": "The `avg_amount_usd` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / canonicalSha256

Added value: +{
+  "description": "The `canonicalSha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / dispute_count

Added value: +{
+  "description": "The `dispute_count` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / disputes

Added value: +{
+  "description": "The `disputes` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / ed25519Sig

Added value: +{
+  "description": "The `ed25519Sig` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / events

Added value: +{
+  "description": "The `events` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / evidence

Added value: +{
+  "description": "The `evidence` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / fails

Added value: +{
+  "description": "The `fails` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / figuresProvided

Added value: +{
+  "description": "The `figuresProvided` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / framing

Added value: +{
+  "description": "The `framing` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / freshness

Added value: +{
+  "description": "The `freshness` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / metrics

Added value: +{
+  "description": "The `metrics` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / missingFields

Added value: +{
+  "description": "The `missingFields` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / observations

Added value: +{
+  "description": "The `observations` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / observed_outcomes

Added value: +{
+  "description": "The `observed_outcomes` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / outcome

Added value: +{
+  "description": "The `outcome` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / providedFields

Added value: +{
+  "description": "The `providedFields` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / publicKeyHex

Added value: +{
+  "description": "The `publicKeyHex` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / reputation_score

Added value: +{
+  "description": "The `reputation_score` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signedBy

Added value: +{
+  "description": "The `signedBy` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / success_rate

Added value: +{
+  "description": "The `success_rate` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / successes

Added value: +{
+  "description": "The `successes` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / total_amount_usd

Added value: +{
+  "description": "The `total_amount_usd` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / ts

Added value: +{
+  "description": "The `ts` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verdictLevel

Added value: +{
+  "description": "The `verdictLevel` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioural context: the score is derived from dated, signed events rather than self-reported data, which tells the agent how much to trust the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the purpose, but the second clause reads as awkwardly truncated ('not agent verdict; an object with 34 fields including activity, agent'). The return-shape detail is also redundant given an output schema exists.

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?

With annotations covering safety and an output schema covering returns, the description only needs to add provenance and sibling routing, which it does. The odd mention of 34 fields is unnecessary but harmless.

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 description coverage is 100% and the two parameters are documented in the schema, so the description need not restate them. It adds no syntax, format, or filtering guidance for `agent` or `events`, so baseline 3 applies.

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 states the resource and, more usefully, the data source: reputation scored from dated, signed behaviour events rather than self-reported. It also explicitly differentiates from the closest sibling (assess_agent_verdict). The phrasing is slightly garbled, which keeps it from a 5.

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 gives an explicit routing rule: use this rather than `assess_agent_verdict` for agent reputation, not agent verdict. That is a real when-to-use signal against an alternative, though it does not spell out exclusions or prerequisites.

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

All Synthex Forge — x402 Paid Agent Services tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.