Synthex Forge — x402 Paid Agent Services

Get Bio Research Reviews

get_bio_research_reviews

Read-onlyIdempotent

BioTrust Service 11 — the Dual-Use Research Review Assistant. use it rather than assess_bio_risk for bio research reviews, not bio risk; an object with 34 fields including action, actor. $1.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.
`action`	No	The action being recorded or evaluated.
`reason`	No	Why the action is being taken. Recorded verbatim in the signed artifact.
`added_by`	No	The added by this operation operates on. See the schema for its type and whether it is required.
`decision`	No	The decision this operation operates on. See the schema for its type and whether it is required.
`evidence`	No	The evidence supporting the claim, as a list of named documents or URLs.
`reviewer`	No	The reviewer this operation operates on. See the schema for its type and whether it is required.
`rationale`	No	The rationale this operation operates on. See the schema for its type and whether it is required.
`review_id`	No	The review id 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.
`created_by`	No	The created by this operation operates on. See the schema for its type and whether it is required.
`flagged_by`	No	The flagged by this operation operates on. See the schema for its type and whether it is required.
`assigned_by`	No	The assigned by this operation operates on. See the schema for its type and whether it is required.
`category_id`	No	The category id this operation operates on. See the schema for its type and whether it is required.
`escalate_to`	No	The escalate to this operation operates on. See the schema for its type and whether it is required.
`escalated_by`	No	The escalated by this operation operates on. See the schema for its type and whether it is required.
`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.
`review_quorum`	No	The review quorum this operation operates on. See the schema for its type and whether it is required.
`institutional_policy_ref`	No	The institutional policy ref 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.
`text`	No	The `text` field of the response.
`actor`	No	The `actor` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`label`	No	The `label` field of the response.
`state`	No	The `state` field of the response.
`action`	No	The `action` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`quorum`	No	The `quorum` field of the response.
`reason`	No	Why the verdict was reached.
`review`	No	The `review` field of the response.
`history`	No	The `history` field of the response.
`evidence`	No	The `evidence` field of the response.
`to_state`	No	The `to_state` field of the response.
`decisions`	No	The `decisions` field of the response.
`review_id`	No	The `review_id` field of the response.
`reviewers`	No	The `reviewers` field of the response.
`block_list`	No	The `block_list` field of the response.
`categories`	No	The `categories` field of the response.
`created_at`	No	The `created_at` field of the response.
`created_by`	No	The `created_by` field of the response.
`escalation`	No	The `escalation` field of the response.
`flagged_by`	No	The `flagged_by` field of the response.
`from_state`	No	The `from_state` field of the response.
`updated_at`	No	The `updated_at` field of the response.
`category_id`	No	The `category_id` field of the response.
`escalations`	No	The `escalations` field of the response.
`subject_hash`	No	The `subject_hash` field of the response.
`quorum_required`	No	The `quorum_required` field of the response.
`rationale_sha256`	No	The `rationale_sha256` field of the response.
`flagged_categories`	No	The `flagged_categories` field of the response.
`institutional_policy_ref`	No	The `institutional_policy_ref` field of the response.
`previous_quorum_required`	No	The `previous_quorum_required` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed36 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 / at

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

addedOutput schema / properties / block_list

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

addedOutput schema / properties / categories

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

addedOutput schema / properties / category_id

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

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

addedOutput schema / properties / decisions

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / error

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

addedOutput schema / properties / escalation

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

addedOutput schema / properties / escalations

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

addedOutput schema / properties / evidence

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

addedOutput schema / properties / flagged_by

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

addedOutput schema / properties / flagged_categories

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

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / label

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

addedOutput schema / properties / previous_quorum_required

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

addedOutput schema / properties / quorum

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

addedOutput schema / properties / quorum_required

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

addedOutput schema / properties / rationale_sha256

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / review

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

addedOutput schema / properties / review_id

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

addedOutput schema / properties / reviewers

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

Added value: +{
+  "description": "The `text` 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 / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful cost information ('$1.5 USDC') and a rough output shape, but does not describe auth requirements, rate limits, or other behavioral details beyond what the annotations and output schema provide.

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

Conciseness4/5

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

The description is compact and front-loads the service identity and the key alternative. It is telegraphic and fragmentary, but almost every element earns its place by conveying routing, output shape, or cost.

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?

For a complex 20-parameter tool, the description gives only high-level routing, a rough output field count, and pricing. The schema and output schema carry much of the burden, but the description does not explain what a 'bio research review' is, how the many optional parameters relate to one another, or how this differs from the broader set of bio-related siblings.

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 schema itself is the primary source of parameter meaning. The description mentions 'action' and 'actor', but 'actor' is not an input parameter and the reference is ambiguous, so it adds little reliable semantic value for the 20 input parameters.

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 identifies the tool as the 'Dual-Use Research Review Assistant' and says it is for bio research reviews rather than bio risk. However, it never clearly states the operation in verb+resource terms, such as retrieving or listing review records, so the purpose remains somewhat vague despite the domain being named.

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 routes the agent away from `assess_bio_risk` and states that this tool is for bio research reviews, not bio risk. That is a clear alternative and condition, though no further when-to-use or exclusion guidance is provided.

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.