Synthex Forge — x402 Paid Agent Services

Create Signed Research Brief

create_signed_research_brief

Destructive

A researched brief on a topic with its sources and depth. use it rather than get_signed_research_brief for signed research brief specifically; an object with 20 fields including algorithm, brief. $2 USDC.

Input Schema

Name	Required	Description	Default
`depth`	No	The depth this operation operates on. See the schema for its type and whether it is required.	brief
`topic`	No	The topic the operation concerns.
`context`	No	Free-form context the operation needs but does not model as a structured field.

Output Schema

Name	Required	Description
`note`	No	A note on how the answer was produced.
`brief`	No	The `brief` field of the response.
`depth`	No	The `depth` field of the response.
`notes`	No	The `notes` field of the response.
`title`	No	The `title` field of the response.
`topic`	No	The `topic` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`signer`	No	The `signer` field of the response.
`sources`	No	The `sources` field of the response.
`summary`	No	One-line summary of the answer.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`disclaimer`	No	The `disclaimer` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`key_points`	No	The `key_points` field of the response.
`generatedAt`	No	The `generatedAt` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / brief

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / depth

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / disclaimer

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

addedOutput schema / properties / ed25519Sig

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

addedOutput schema / properties / generatedAt

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

addedOutput schema / properties / key_points

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

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

addedOutput schema / properties / signer

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

addedOutput schema / properties / sources

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

removedOutput schema / properties / status

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

addedOutput schema / properties / summary

Added value: +{
+  "description": "One-line summary of the answer.",
+  "type": "string"
+}

addedOutput schema / properties / title

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

addedOutput schema / properties / topic

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

addedOutput schema / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false. The description adds the genuinely useful disclosure of a $2 USDC cost, which the annotations do not convey. However it does not warn that this is a destructive/charged mutation, and the framing as a 'brief... with its sources' nudges toward a read interpretation, undercutting the destructiveHint signal.

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?

It is short, but the structure is garbled: the sibling comparison is tautological, and the trailing 'an object with 20 fields including algorithm, brief' fragment is abrupt and belongs in an output schema that already exists. Sentences do not earn their place.

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?

For a destructive, paid creation tool, the description omits what is actually created/signed, what 'depth' options exist, and what happens on repeated calls (non-idempotent). It leans on the output schema for return values, which is fine, but the behavioral and usage context an agent needs before spending $2 USDC is thin.

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%, so the parameters are already documented; the baseline of 3 applies. The description mentions 'topic' and 'depth' but adds no format, range, or allowed-value detail beyond what the schema provides, and ignores 'context' entirely.

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 a resource (a researched brief on a topic with sources and depth) and does name a sibling, but it reads as describing the output artifact rather than the create action. The clause 'use it rather than `get_signed_research_brief` for signed research brief specifically' is tautological and muddies whether this creates or retrieves, so the verb/resource pairing is not crisply established.

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 a sibling reference ('use it rather than get_signed_research_brief'), but the stated condition ('for signed research brief specifically') is vacuous since the tool is by definition for that. No genuine when-to-use, prerequisites, or cost-justification guidance is given despite the operation being paid ($2 USDC).

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.