Synthex Forge — x402 Paid Agent Services

Search Forensics Evidence

search_forensics_evidence

Read-onlyIdempotent

Querying that vault by actor or predicate. use it rather than create_audit_evidence_package for forensics evidence, not audit evidence package; an object with 20 fields including actorFilter, algorithm. $0.15 USDC.

Input Schema

Name	Required	Description	Default
`entries`	No	The entries this operation operates on. See the schema for its type and whether it is required.
`actor_did`	No	The actor did this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`entries`	No	The `entries` field of the response.
`receipt`	No	The `receipt` field of the response.
`verdict`	Yes	The decision this tool returned.
`entryIds`	No	The `entryIds` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`queriedAt`	No	The `queriedAt` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`entryCount`	No	The `entryCount` field of the response.
`actorFilter`	No	The `actorFilter` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`invalidEntriesSkipped`	No	The `invalidEntriesSkipped` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 31, 2026

addedOutput schema / properties / actorFilter

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

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` 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 / ed25519Sig

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

addedOutput schema / properties / entries

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

addedOutput schema / properties / entryCount

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

addedOutput schema / properties / entryIds

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

addedOutput schema / properties / invalidEntriesSkipped

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

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` 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 / publicKeyHex

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

addedOutput schema / properties / queriedAt

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

addedOutput schema / properties / receipt

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

addedOutput schema / properties / reproducibility

Added value: +{
+  "description": "The `reproducibility` 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 / 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

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds one genuinely new behavioral fact not in annotations: the call costs $0.15 USDC, which is useful for agent budgeting. Beyond the price, it discloses nothing about scope or result behavior.

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

Conciseness2/5

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

Two fragmented clauses with a dangling reference ('that vault'), an awkward negated comparison, and a price tag appended without a sentence frame. Short in length but not front-loaded or coherently structured.

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?

An output schema exists so return values needn't be explained, but the description leaves the core question unanswered: what corpus is being searched and what 'entries' or 'actor_did' mean in this context. The '20 fields' claim further obscures rather than completes the picture.

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?

Schema coverage is 100%, so baseline is 3, but the description's parameter talk actively misleads: it cites 'an object with 20 fields including actorFilter, algorithm,' while the actual schema exposes only entries and actor_did. That mismatch risks an agent constructing arguments that do not exist.

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 frames the tool as a query over a vault 'by actor or predicate,' which roughly matches the name's search semantics, but the referent 'that vault' has no antecedent and the object it describes is never named. An agent can guess this searches forensics evidence, but it is guessing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names an alternative, 'use it rather than create_audit_evidence_package,' and clarifies it targets forensics evidence rather than audit evidence packages. However, the contrast is muddled since that sibling creates packages rather than searching them, and no positive trigger condition (what query, what situation) is given.

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.