Synthex Forge — x402 Paid Agent Services

Assess Bio Risk

assess_bio_risk

Read-onlyIdempotent

BioTrust Service 01 — BioRisk. use it rather than create_bio_audit_receipt for bio risk, not bio audit receipt; an object with 46 fields including activity_modifiers, advisory_only. $2 USDC.

Input Schema

Name	Required	Description	Default
`as_of`	No	The date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
`work_type`	No	The work type this operation operates on. See the schema for its type and whether it is required.
`policy_ref`	No	Identifier of the policy the decision is bound to.
`project_id_hash`	No	The project id hash this operation operates on. See the schema for its type and whether it is required.
`agent_risk_group`	No	The agent risk group this operation operates on. See the schema for its type and whether it is required.	unknown
`containment_level`	No	The containment level this operation operates on. See the schema for its type and whether it is required.
`controls_declared`	No	The controls declared this operation operates on. See the schema for its type and whether it is required.
`activity_modifiers`	No	The activity modifiers this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`gap`	No	The `gap` field of the response.
`url`	No	The `url` field of the response.
`kind`	No	The `kind` field of the response.
`step`	No	The `step` field of the response.
`as_of`	No	The date the answer is computed as of.
`basis`	No	The `basis` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`title`	No	The `title` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`licence`	No	The `licence` field of the response.
`rule_id`	No	The `rule_id` field of the response.
`version`	No	The `version` field of the response.
`citation`	No	The `citation` field of the response.
`publisher`	No	The `publisher` field of the response.
`risk_tier`	No	The `risk_tier` field of the response.
`source_id`	No	The `source_id` field of the response.
`work_type`	No	The `work_type` field of the response.
`policy_ref`	No	The `policy_ref` field of the response.
`provenance`	No	The `provenance` field of the response.
`is_official`	No	The `is_official` field of the response.
`rules_fired`	No	The `rules_fired` field of the response.
`control_gaps`	No	The `control_gaps` field of the response.
`jurisdiction`	No	The `jurisdiction` field of the response.
`published_at`	No	The `published_at` field of the response.
`retrieved_at`	No	The `retrieved_at` field of the response.
`review_steps`	No	The `review_steps` field of the response.
`advisory_only`	No	The `advisory_only` field of the response.
`framework_refs`	No	The `framework_refs` field of the response.
`matrix_version`	No	The `matrix_version` field of the response.
`tier_driven_by`	No	The `tier_driven_by` field of the response.
`project_id_hash`	No	The `project_id_hash` field of the response.
`agent_risk_group`	No	The `agent_risk_group` field of the response.
`information_gaps`	No	The `information_gaps` field of the response.
`missing_controls`	No	The `missing_controls` field of the response.
`containment_level`	No	The `containment_level` field of the response.
`controls_declared`	No	The `controls_declared` field of the response.
`modifiers_applied`	No	The `modifiers_applied` field of the response.
`activity_modifiers`	No	The `activity_modifiers` field of the response.
`mandatory_controls`	No	The `mandatory_controls` field of the response.
`methodology_version`	No	Version of the method that produced the answer.
`tier_clause_matched`	No	The `tier_clause_matched` field of the response.
`declared_agent_risk_group`	No	The `declared_agent_risk_group` field of the response.
`declared_containment_level`	No	The `declared_containment_level` field of the response.
`declaration_inconsistencies`	No	The `declaration_inconsistencies` field of the response.
`requires_human_verification`	No	The `requires_human_verification` field of the response.
`published_minimum_containment_level`	No	The `published_minimum_containment_level` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed48 schema fields changedOct 31, 2026

addedOutput schema / properties / activity_modifiers

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

addedOutput schema / properties / advisory_only

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

addedOutput schema / properties / agent_risk_group

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

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / basis

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

addedOutput schema / properties / citation

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

addedOutput schema / properties / containment_level

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

addedOutput schema / properties / control_gaps

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

addedOutput schema / properties / controls_declared

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

addedOutput schema / properties / declaration_inconsistencies

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

addedOutput schema / properties / declared_agent_risk_group

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

addedOutput schema / properties / declared_containment_level

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

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

addedOutput schema / properties / gap

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

addedOutput schema / properties / information_gaps

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

addedOutput schema / properties / is_official

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

addedOutput schema / properties / jurisdiction

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / licence

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

addedOutput schema / properties / mandatory_controls

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

addedOutput schema / properties / matrix_version

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

addedOutput schema / properties / methodology_version

Added value: +{
+  "description": "Version of the method that produced the answer.",
+  "type": "string"
+}

addedOutput schema / properties / missing_controls

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

addedOutput schema / properties / modifiers_applied

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

addedOutput schema / properties / policy_ref

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

addedOutput schema / properties / project_id_hash

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

addedOutput schema / properties / provenance

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

addedOutput schema / properties / published_at

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

addedOutput schema / properties / published_minimum_containment_level

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

addedOutput schema / properties / publisher

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

addedOutput schema / properties / requires_human_verification

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

addedOutput schema / properties / retrieved_at

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

addedOutput schema / properties / review_steps

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

addedOutput schema / properties / risk_tier

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

addedOutput schema / properties / rule_id

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

addedOutput schema / properties / rules_fired

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

addedOutput schema / properties / source_id

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

removedOutput schema / properties / status

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

addedOutput schema / properties / step

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

addedOutput schema / properties / tier_clause_matched

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

addedOutput schema / properties / tier_driven_by

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

addedOutput schema / properties / title

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

addedOutput schema / properties / url

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

addedOutput schema / properties / version

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

addedOutput schema / properties / work_type

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

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

AddedOct 31, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description's real addition is the '$2 USDC' cost and the '46 fields including activity_modifiers, advisory_only' output shape, which are useful call-time facts. It stops short of saying how the answer is scoped (e.g. that `as_of` reproduces a past decision) or what 'advisory_only' implies for acting on the result.

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, and the cost and output-size facts are front-loaded enough to be found. But the phrasing is garbled and run-on ('for bio risk, not bio audit receipt; an object with 46 fields...'), and the negative restatement of the sibling name spends words without adding information.

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 the annotations cover the safety profile. Still, for an eight-parameter assessment tool with zero required inputs, the description never says what the assessment decides or how defaults (e.g. `as_of` defaulting to today) affect the answer, leaving the agent to infer the tool's role.

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 eight parameters are already documented and the baseline is 3. The description only names two output fields (`activity_modifiers`, `advisory_only`) rather than explaining any input parameter's meaning or interactions, so it adds no semantic value over the schema.

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 says it is the 'BioRisk' service and explicitly separates it from `create_bio_audit_receipt`, so the agent can tell the two apart. But it never states what the assessment actually produces conceptually (a risk score, a verdict, a decision?) beyond naming two output fields, so the verb+resource pairing stays vague.

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 gives one explicit routing rule — prefer this over `create_bio_audit_receipt` for bio risk — which is genuine when-to-use guidance. However, there are many other bio siblings (`verify_bio_audit`, `run_bio_verification_checks`, `search_bio_compliance`, `get_bio_catalogue`) and no guidance on when to pick this rather than those, nor any when-not conditions.

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.