Synthex Forge — x402 Paid Agent Services

Run Bio Verification Checks

run_bio_verification_checks

Read-onlyIdempotent

BioTrust Service 14 — Registry Verification. use it rather than assess_bio_risk for bio verification checks, not bio risk; an object with 39 fields including Accept, Authorization. $0.75 USDC.

Input Schema

Name	Required	Description
`check`	No	The check this operation operates on. See the schema for its type and whether it is required.
`limit`	No	Maximum number of items to return.
`query`	No	The query the operation runs.
`purpose`	No	The purpose this operation operates on. See the schema for its type and whether it is required.
`min_score`	No	The min score this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`url`	No	The `url` field of the response.
`list`	No	The `list` field of the response.
`name`	No	The `name` field of the response.
`check`	No	The `check` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`limit`	No	The `limit` field of the response.
`lists`	No	The `lists` field of the response.
`query`	No	The `query` field of the response.
`stale`	No	The `stale` field of the response.
`title`	No	The `title` field of the response.
`Accept`	No	The `Accept` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`status`	No	The status of the operation.
`entries`	No	The `entries` field of the response.
`licence`	No	The `licence` field of the response.
`matches`	No	The `matches` field of the response.
`payload`	No	The `payload` field of the response.
`purpose`	No	The `purpose` field of the response.
`verdict`	Yes	The decision this tool returned.
`built_at`	No	The `built_at` field of the response.
`entry_id`	No	The `entry_id` field of the response.
`min_score`	No	The `min_score` field of the response.
`programme`	No	The `programme` field of the response.
`publisher`	No	The `publisher` field of the response.
`User-Agent`	No	The `User-Agent` field of the response.
`confidence`	No	Confidence in the verdict, 0 to 1.
`fetched_at`	No	The `fetched_at` field of the response.
`age_seconds`	No	The `age_seconds` field of the response.
`entity_type`	No	The `entity_type` field of the response.
`source_refs`	No	The `source_refs` field of the response.
`match_method`	No	The `match_method` field of the response.
`matched_name`	No	The `matched_name` field of the response.
`retrieved_at`	No	The `retrieved_at` field of the response.
`Authorization`	No	The `Authorization` field of the response.
`screened_lists`	No	The `screened_lists` field of the response.
`provider_detail`	No	The `provider_detail` field of the response.
`provider_reason`	No	The `provider_reason` field of the response.
`registry_snapshot_at`	No	The `registry_snapshot_at` field of the response.
`human_review_required`	No	The `human_review_required` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed40 schema fields changedOct 31, 2026

addedOutput schema / properties / Accept

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

addedOutput schema / properties / Authorization

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

addedOutput schema / properties / User-Agent

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

addedOutput schema / properties / age_seconds

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

addedOutput schema / properties / built_at

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

addedOutput schema / properties / check

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

addedOutput schema / properties / confidence

Added value: +{
+  "description": "Confidence in the verdict, 0 to 1.",
+  "type": "number"
+}

addedOutput schema / properties / detail

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

addedOutput schema / properties / entity_type

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

addedOutput schema / properties / entries

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

addedOutput schema / properties / entry_id

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

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

addedOutput schema / properties / human_review_required

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

addedOutput schema / properties / licence

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

addedOutput schema / properties / limit

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

addedOutput schema / properties / list

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

addedOutput schema / properties / lists

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

addedOutput schema / properties / match_method

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

addedOutput schema / properties / matched_name

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

addedOutput schema / properties / matches

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

addedOutput schema / properties / min_score

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

addedOutput schema / properties / name

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

addedOutput schema / properties / payload

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

addedOutput schema / properties / programme

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

addedOutput schema / properties / provider_detail

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

addedOutput schema / properties / provider_reason

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

addedOutput schema / properties / publisher

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

addedOutput schema / properties / purpose

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

addedOutput schema / properties / query

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

addedOutput schema / properties / registry_snapshot_at

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

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

addedOutput schema / properties / source_refs

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

addedOutput schema / properties / stale

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

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

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 / verdict

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's genuine addition is the price ("$0.75 USDC"), which tells the agent the call is paid. However, the trailing "an object with 39 fields including Accept, Authorization" describes a return shape that an output schema already covers and that reads like HTTP headers, adding confusion rather than behavioral context.

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 service identity and sibling routing are front-loaded. But the sentence is a semicolon-chained fragment ending in a stray return-shape clause, so it reads as stitched-together boilerplate rather than one earned, well-formed statement.

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?

With annotations covering safety, an output schema present, and 100% schema coverage, most structured burden is borne elsewhere, and the description supplies the price and the sibling routing. Still missing is any sense of which checks are available or what a registry verification actually returns conceptually, which matters for a 5-parameter sparse tool with no required fields.

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 documents all five parameters and the baseline of 3 applies. The description adds nothing about `check`, `query`, `purpose` or `min_score` — no example values, no indication of what a check identifier looks like — but it also doesn't mislead.

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 a specific service (BioTrust Service 14 — Registry Verification) and a specific verb+resource (run bio verification checks), and it explicitly separates the tool from the sibling `assess_bio_risk`. What a 'verification check' actually consists of is left unstated, but the sibling differentiation makes the tool selectable.

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?

"use it rather than `assess_bio_risk` for bio verification checks, not bio risk" is an explicit routing instruction with a named alternative, which is exactly the guidance an agent needs against a large sibling set. It gives no other when/when-not conditions or prerequisites, but the one disambiguation it provides is the important one.

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.