Synthex Forge — x402 Paid Agent Services

Search Bio Compliance

search_bio_compliance

Read-onlyIdempotent

BioTrust Service 02 — answer ONE compliance question, with citations. use it rather than assess_bio_risk for bio compliance, not bio risk; an object with 48 fields including added, answers. $0.5 USDC.

Input Schema

Name	Required	Description
`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.
`query`	No	The query the operation runs.
`top_k`	No	The top k this operation operates on. See the schema for its type and whether it is required.
`compare`	No	The compare this operation operates on. See the schema for its type and whether it is required.
`source_ids`	No	The source ids this operation operates on. See the schema for its type and whether it is required.
`jurisdiction`	No	The jurisdiction the answer applies to. Accepts an ISO-3166 alpha-2 code or a country name.

Output Schema

Name	Required	Description
`key`	No	The `key` field of the response.
`url`	No	The `url` field of the response.
`why`	No	The `why` field of the response.
`mode`	No	The `mode` field of the response.
`added`	No	The `added` field of the response.
`doc_a`	No	The `doc_a` field of the response.
`doc_b`	No	The `doc_b` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`field`	No	The `field` field of the response.
`title`	No	The `title` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`doc_id`	No	The `doc_id` field of the response.
`result`	No	The `result` field of the response.
`status`	No	The status of the operation.
`values`	No	The `values` field of the response.
`answers`	No	The `answers` field of the response.
`changed`	No	The `changed` field of the response.
`excerpt`	No	The `excerpt` field of the response.
`heading`	No	The `heading` field of the response.
`licence`	No	The `licence` field of the response.
`removed`	No	The `removed` field of the response.
`version`	No	The `version` field of the response.
`built_at`	No	The `built_at` field of the response.
`sections`	No	The `sections` field of the response.
`conflicts`	No	The `conflicts` field of the response.
`doc_count`	No	The `doc_count` field of the response.
`freshness`	No	The `freshness` field of the response.
`identical`	No	The `identical` field of the response.
`publisher`	No	The `publisher` field of the response.
`comparison`	No	The `comparison` field of the response.
`heading_id`	No	The `heading_id` field of the response.
`unreachable`	No	The `unreachable` 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.
`text_excerpt`	No	The `text_excerpt` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`section_count`	No	The `section_count` field of the response.
`content_sha256`	No	The `content_sha256` field of the response.
`corpus_snapshot`	No	The `corpus_snapshot` field of the response.
`differing_terms`	No	The `differing_terms` field of the response.
`metadata_deltas`	No	The `metadata_deltas` field of the response.
`reachable_count`	No	The `reachable_count` field of the response.
`relevance_score`	No	The `relevance_score` field of the response.
`freshness_detail`	No	The `freshness_detail` field of the response.
`content_sha256_after`	No	The `content_sha256_after` field of the response.
`content_sha256_before`	No	The `content_sha256_before` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed49 schema fields changedOct 31, 2026

addedOutput schema / properties / added

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

addedOutput schema / properties / answers

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

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

addedOutput schema / properties / comparison

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

addedOutput schema / properties / conflicts

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

addedOutput schema / properties / content_sha256

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

addedOutput schema / properties / content_sha256_after

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

addedOutput schema / properties / content_sha256_before

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

addedOutput schema / properties / corpus_snapshot

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

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / differing_terms

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

addedOutput schema / properties / doc_a

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

addedOutput schema / properties / doc_b

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

addedOutput schema / properties / doc_count

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

addedOutput schema / properties / doc_id

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

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

addedOutput schema / properties / field

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

addedOutput schema / properties / freshness

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

addedOutput schema / properties / freshness_detail

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

addedOutput schema / properties / heading

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

addedOutput schema / properties / heading_id

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

addedOutput schema / properties / identical

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

addedOutput schema / properties / jurisdiction

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

addedOutput schema / properties / key

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

addedOutput schema / properties / licence

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

addedOutput schema / properties / metadata_deltas

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

addedOutput schema / properties / mode

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

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

addedOutput schema / properties / reachable_count

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

addedOutput schema / properties / relevance_score

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

addedOutput schema / properties / removed

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

addedOutput schema / properties / result

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

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

addedOutput schema / properties / sections

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

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

addedOutput schema / properties / text_excerpt

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

addedOutput schema / properties / title

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

addedOutput schema / properties / unreachable

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

addedOutput schema / properties / url

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

addedOutput schema / properties / value

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

addedOutput schema / properties / values

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

addedOutput schema / properties / version

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

addedOutput schema / properties / why

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

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

AddedOct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: answers carry citations and each call costs $0.5 USDC — a cost signal an agent needs before invoking. It does not explain payment/auth mechanics or why the field list is 48 wide, and the 'added, answers' fragment is garbled.

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?

Very short and front-loads the purpose, which is good. But two of its four clauses are incoherent template residue ('BioTrust Service 02 —', 'an object with 48 fields including added, answers') that consume space without conveying usable information, dragging down the efficiency of an otherwise tight description.

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 and annotations cover safety, so the description needn't explain returns; it does anyway, badly. What remains underspecified is the domain scope of a 'compliance question' and how the citation/source model interacts with `source_ids` and `jurisdiction`. Cost and the sibling contrast are the meaningful additions; the rest of the description is adequate but leaves gaps.

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 all six parameters (as_of, query, top_k, compare, source_ids, jurisdiction) are documented in the schema itself. The description adds only the indirect hint that one question is answered per call, which narrows how `query` should be used, but says nothing about as_of, top_k, compare, or jurisdiction semantics. Baseline 3 applies.

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?

States a specific action and object ('answer ONE compliance question, with citations') and explicitly distinguishes itself from the sibling `assess_bio_risk` by domain ('bio compliance, not bio risk'). The stray 'BioTrust Service 02 —' prefix and the fragment 'an object with 48 fields including added, answers' add noise, but the core verb+resource+scope is unmistakable.

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?

Names the alternative tool (`assess_bio_risk`) and the condition that selects this one: compliance, not risk. It also signals a per-call constraint ('ONE compliance question'), implying one question per invocation rather than a batch. No explicit when-not guidance beyond the sibling contrast.

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.