Synthex Forge — x402 Paid Agent Services

Create Security Threat Model

create_security_threat_model

Destructive

Threatmodel Analyze. use it rather than run_agent_security_scan for security threat model, not agent security scan; an object with 32 fields including algorithm, analyzed_at. $0.25 USDC.

Input Schema

Name	Required	Description	Default
`tool_manifest`	No	The tool manifest this operation operates on. See the schema for its type and whether it is required.
`deployment_context`	No	The deployment context this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`auth`	No	The `auth` field of the response.
`kind`	No	The `kind` field of the response.
`name`	No	The `name` 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.
`verdict`	Yes	The decision this tool returned.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`stored_at`	No	The `stored_at` field of the response.
`tool_name`	No	The `tool_name` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`risk_grade`	No	The `risk_grade` field of the response.
`risk_score`	No	The `risk_score` field of the response.
`analyzed_at`	No	The `analyzed_at` field of the response.
`description`	No	The `description` field of the response.
`permissions`	No	The `permissions` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`threat_model`	No	The `threat_model` field of the response.
`attack_vectors`	No	The `attack_vectors` field of the response.
`attestation_id`	No	The `attestation_id` field of the response.
`evidenceDigest`	No	The `evidenceDigest` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`recommendations`	No	The `recommendations` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`escalation_paths`	No	The `escalation_paths` field of the response.
`verificationHint`	No	The `verificationHint` field of the response.
`deployment_context`	No	The `deployment_context` field of the response.
`high_risk_permissions`	No	The `high_risk_permissions` field of the response.
`permissions_catalogued`	No	The `permissions_catalogued` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / analyzed_at

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

addedOutput schema / properties / attack_vectors

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

addedOutput schema / properties / attestation_id

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

addedOutput schema / properties / auth

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / deployment_context

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

addedOutput schema / properties / description

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

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

addedOutput schema / properties / evidenceCore

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

addedOutput schema / properties / evidenceDigest

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

addedOutput schema / properties / high_risk_permissions

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / name

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

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

addedOutput schema / properties / permissions_catalogued

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / recommendations

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / risk_grade

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

addedOutput schema / properties / risk_score

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

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

addedOutput schema / properties / threat_model

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

addedOutput schema / properties / tool_name

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / verificationHint

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds value by disclosing cost ('$0.25 USDC') and output shape ('32 fields including algorithm, analyzed_at'), but never addresses what the destructive operation actually does or requires, leaving a gap for a mutation tool.

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, but not cleanly structured: it begins with a verbless fragment, then splices routing, output shape, and pricing together with semicolons. Nothing blatantly wasteful, but the ordering buries the clearest information and the front-load is weak.

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 values needn't be explained, and annotations carry the safety profile. Still, for a destructive, paid, non-idempotent tool the description should clarify what the analysis produces or what is affected; as written it is minimally sufficient but not complete.

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 both parameters (tool_manifest, deployment_context) are documented in the schema. The description adds no parameter-level meaning beyond that, which is the correct baseline of 3 when the schema does the lifting.

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 opens with the fragment 'Threatmodel Analyze,' which is vague and doesn't clearly state a create verb matching the tool name 'create_security_threat_model.' It does, however, distinguish it from `run_agent_security_scan` by scope ('security threat model, not agent security scan'), giving an agent a differentiation cue despite the mushy purpose statement.

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 explicitly names the alternative ('use it rather than `run_agent_security_scan`') and scopes the condition ('for security threat model, not agent security scan'). The phrasing is somewhat circular, but the alternative-and-condition routing is clearly present.

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.