Synthex Forge — x402 Paid Agent Services

Execute Bio Workflow

execute_bio_workflow

Destructive

BioTrust Service 10 — the Biorisk Workflow Manager. use it rather than assess_bio_risk for bio workflow, not bio risk; an object with 28 fields including action, actor. $0.5 USDC.

Input Schema

Name	Required	Description
`role`	No	The role this operation operates on. See the schema for its type and whether it is required.
`actor`	No	Who performed the action. Used to attribute the record and to check the authority of the caller.
`action`	No	The action being recorded or evaluated.
`due_at`	No	The due at this operation operates on. See the schema for its type and whether it is required.
`reason`	No	Why the action is being taken. Recorded verbatim in the signed artifact.
`filters`	No	The filters this operation operates on. See the schema for its type and whether it is required.
`assignee`	No	The assignee this operation operates on. See the schema for its type and whether it is required.
`conditions`	No	The conditions that must hold for the answer to be positive.
`escalate_to`	No	The escalate to this operation operates on. See the schema for its type and whether it is required.
`workflow_id`	No	The identifier of the workflow.
`subject_hash`	No	The subject hash this operation operates on. See the schema for its type and whether it is required.
`justification`	No	The justification this operation operates on. See the schema for its type and whether it is required.
`workflow_type`	No	The workflow type this operation operates on. See the schema for its type and whether it is required.
`policy_version`	No	Version of the policy the decision is bound to.
`required_roles`	No	The required roles this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`at`	No	The `at` field of the response.
`kind`	No	The `kind` field of the response.
`actor`	No	The `actor` field of the response.
`count`	No	The `count` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`state`	No	The `state` field of the response.
`action`	No	The `action` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`due_at`	No	The `due_at` field of the response.
`creator`	No	The `creator` field of the response.
`history`	No	The `history` field of the response.
`to_state`	No	The `to_state` field of the response.
`workflow`	No	The `workflow` field of the response.
`approvals`	No	The `approvals` field of the response.
`workflows`	No	The `workflows` field of the response.
`created_at`	No	The `created_at` field of the response.
`from_state`	No	The `from_state` field of the response.
`updated_at`	No	The `updated_at` field of the response.
`assignments`	No	The `assignments` field of the response.
`escalations`	No	The `escalations` field of the response.
`workflow_id`	No	The `workflow_id` field of the response.
`subject_hash`	No	The `subject_hash` field of the response.
`justification`	No	The `justification` field of the response.
`workflow_type`	No	The `workflow_type` field of the response.
`policy_version`	No	The `policy_version` field of the response.
`required_roles`	No	The `required_roles` field of the response.
`justification_sha256`	No	The `justification_sha256` field of the response.
`justification_excerpt`	No	The `justification_excerpt` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed30 schema fields changedOct 31, 2026

addedOutput schema / properties / action

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

addedOutput schema / properties / actor

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

addedOutput schema / properties / approvals

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

addedOutput schema / properties / assignments

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

addedOutput schema / properties / at

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

addedOutput schema / properties / count

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

addedOutput schema / properties / created_at

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

addedOutput schema / properties / creator

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / due_at

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

addedOutput schema / properties / error

Added value: +{
+  "description": "The machine-readable error code, when the operation failed.",
+  "type": "string"
+}

addedOutput schema / properties / escalations

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

addedOutput schema / properties / from_state

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

addedOutput schema / properties / history

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

addedOutput schema / properties / justification

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

addedOutput schema / properties / justification_excerpt

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

addedOutput schema / properties / justification_sha256

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / policy_version

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

addedOutput schema / properties / required_roles

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

addedOutput schema / properties / state

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

removedOutput schema / properties / status

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

addedOutput schema / properties / subject_hash

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

addedOutput schema / properties / to_state

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

addedOutput schema / properties / updated_at

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

addedOutput schema / properties / workflow

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

addedOutput schema / properties / workflow_id

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

addedOutput schema / properties / workflow_type

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

addedOutput schema / properties / workflows

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

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

AddedOct 31, 2026

TDQS

B3/5.0

Behavior2/5

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

Annotations already declare this tool is destructive, non-read-only, and non-idempotent. The description adds a price ('$0.5 USDC') but does not explain what executing a workflow changes, what may be destroyed, whether authorization is required, or what side effects to expect from a destructive operation.

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?

The description is short and front-loads the service identity, but the grammar and punctuation are awkward, and the semicolon-separated clause about fields is unclear. It is concise without being well-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?

Although an output schema exists and the input schema is fully described, this is a destructive, non-idempotent workflow tool with 15 parameters. The description does not explain what a workflow execution actually does, what preconditions exist, or what safety-relevant behavior an agent should anticipate.

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 the input schema already documents all 15 parameters. The description's only parameter-related statement is that the object has 28 fields including action and actor, which is vague and conflicts with the 15-property schema, so it adds confusion rather than useful semantics.

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 names the service and positions it as the 'Biorisk Workflow Manager,' and explicitly distinguishes it from `assess_bio_risk` by saying it is for bio workflow rather than bio risk. The purpose is clear enough to route an agent, though the phrase 'an object with 28 fields' is ambiguous and does not cleanly state the action performed.

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 a direct alternative: use this rather than `assess_bio_risk` for bio workflow. That is a concrete when-to-use signal. It does not address other plausible bio siblings such as verification or audit tools, so it stops short of full guidance.

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.