Synthex Forge — x402 Paid Agent Services

Get Bio Catalogue

get_bio_catalogue

Read-onlyIdempotent

BioTrust Service 07 — the machine-readable index of this namespace. use it rather than assess_bio_risk for bio catalogue, not bio risk; an object with 28 fields including count, detail. $0.02 USDC.

Input Schema

Name	Required	Description
`service_id`	No	The service id this operation operates on. See the schema for its type and whether it is required.
`include_schemas`	No	The include schemas this operation operates on. See the schema for its type and whether it is required.
`include_limitations`	No	The include limitations this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`path`	No	The `path` field of the response.
`count`	No	The `count` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`route`	No	The `route` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`limits`	No	The `limits` field of the response.
`method`	No	The `method` field of the response.
`result`	No	The `result` field of the response.
`status`	No	The status of the operation.
`summary`	No	One-line summary of the answer.
`services`	No	The `services` field of the response.
`namespace`	No	The `namespace` field of the response.
`price_usd`	No	The price of the operation that was paid.
`price_rail`	No	The `price_rail` field of the response.
`service_id`	No	The `service_id` field of the response.
`live_atomic`	No	The `live_atomic` field of the response.
`price_atomic`	No	The `price_atomic` field of the response.
`mcp_tool_name`	No	The `mcp_tool_name` field of the response.
`spine_version`	No	The `spine_version` field of the response.
`price_currency`	No	The `price_currency` field of the response.
`proposed_count`	No	The `proposed_count` field of the response.
`include_schemas`	No	The `include_schemas` field of the response.
`service_version`	No	The `service_version` field of the response.
`value_rationale`	No	The `value_rationale` field of the response.
`implemented_count`	No	The `implemented_count` field of the response.
`request_model_name`	No	The `request_model_name` field of the response.
`include_limitations`	No	The `include_limitations` field of the response.
`price_agrees_with_live_route`	No	The `price_agrees_with_live_route` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 31, 2026

addedOutput schema / properties / count

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

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

addedOutput schema / properties / include_limitations

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

addedOutput schema / properties / include_schemas

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

addedOutput schema / properties / limits

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

addedOutput schema / properties / live_atomic

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

addedOutput schema / properties / mcp_tool_name

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

addedOutput schema / properties / method

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

addedOutput schema / properties / namespace

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

addedOutput schema / properties / path

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

addedOutput schema / properties / price_agrees_with_live_route

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

addedOutput schema / properties / price_atomic

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

addedOutput schema / properties / price_currency

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

addedOutput schema / properties / price_rail

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

addedOutput schema / properties / price_usd

Added value: +{
+  "description": "The price of the operation that was paid.",
+  "type": "number"
+}

addedOutput schema / properties / proposed_count

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

addedOutput schema / properties / request_model_name

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

addedOutput schema / properties / result

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

addedOutput schema / properties / route

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

addedOutput schema / properties / service_id

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

addedOutput schema / properties / service_version

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

addedOutput schema / properties / services

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

addedOutput schema / properties / spine_version

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

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

addedOutput schema / properties / summary

Added value: +{
+  "description": "One-line summary of the answer.",
+  "type": "string"
+}

addedOutput schema / properties / value_rationale

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

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

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: a concrete price ('$0.02 USDC') and a rough payload shape ('an object with 28 fields including count, detail'). It does not mention pagination or auth needs, which keeps it at 4 rather than 5.

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 front-loads the resource identity, which is good. However, the phrasing is clunky and partly redundant ('use it rather than assess_bio_risk for bio catalogue, not bio risk') and the 'BioTrust Service 07' label is internal noise that does not help tool selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return-value summary is extra but harmless. Combined with full schema coverage and complete annotations, the description covers purpose, the alternative to avoid, and cost — enough for correct invocation. Missing only usage-side details like pagination or response size limits for large catalogues.

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 three parameters (service_id, include_schemas, include_limitations) are already documented in the schema. The description adds no additional meaning about what these parameters control or how they affect the response, so the 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 it is 'the machine-readable index of this namespace' for BioTrust, which is a specific enough resource characterization to tell it apart from the assess_* family. It explicitly names the sibling it must not be confused with (assess_bio_risk) and clarifies 'bio catalogue, not bio risk'. The 'Service 07' prefix and 'this namespace' are slightly opaque, keeping it from a 5.

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?

Explicitly routes the agent: 'use it rather than `assess_bio_risk` for bio catalogue, not bio risk' names both the alternative and the condition that selects this tool. No when-not or prerequisite guidance (e.g., auth, rate limits) is given, so it stops short of a 5.

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.