Synthex Forge — x402 Paid Agent Services

Get Bio Outbreak Events

get_bio_outbreak_events

Read-onlyIdempotent

BioTrust Service 05 — the OutbreakSignal. use it rather than get_bio_labcyber_events for bio outbreak events, not bio labcyber events; an object with 33 fields including Accept, User-Agent. $0.05 USDC.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of items to return.
`since`	No	The since this operation operates on. See the schema for its type and whether it is required.
`until`	No	The until this operation operates on. See the schema for its type and whether it is required.
`refresh`	No	The refresh this operation operates on. See the schema for its type and whether it is required.
`category`	No	The category this operation operates on. See the schema for its type and whether it is required.
`geography`	No	The geography 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.

Output Schema

Name	Required	Description
`url`	No	The `url` field of the response.
`kind`	No	The `kind` field of the response.
`count`	No	The `count` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`field`	No	The `field` field of the response.
`items`	No	The items the operation returned.
`title`	No	The `title` field of the response.
`Accept`	No	The `Accept` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`events`	No	The `events` 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.
`sources`	No	The `sources` field of the response.
`summary`	No	One-line summary of the answer.
`category`	No	The `category` field of the response.
`event_id`	No	The `event_id` field of the response.
`revision`	No	The `revision` field of the response.
`geography`	No	The `geography` field of the response.
`last_seen`	No	The `last_seen` field of the response.
`publisher`	No	The `publisher` field of the response.
`source_id`	No	The `source_id` field of the response.
`title_key`	No	The `title_key` field of the response.
`User-Agent`	No	The `User-Agent` field of the response.
`fetched_at`	No	The `fetched_at` field of the response.
`first_seen`	No	The `first_seen` field of the response.
`from_cache`	No	The `from_cache` field of the response.
`item_count`	No	The `item_count` field of the response.
`published_at`	No	The `published_at` field of the response.
`last_modified`	No	The `last_modified` field of the response.
`revision_count`	No	The `revision_count` field of the response.
`source_freshness`	No	The `source_freshness` field of the response.
`source_disagreements`	No	The `source_disagreements` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedOct 31, 2026

addedOutput schema / properties / Accept

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

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

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

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

addedOutput schema / properties / events

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

addedOutput schema / properties / fetched_at

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

addedOutput schema / properties / field

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

addedOutput schema / properties / first_seen

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

addedOutput schema / properties / from_cache

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

addedOutput schema / properties / geography

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

addedOutput schema / properties / item_count

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

addedOutput schema / properties / items

Added value: +{
+  "description": "The items the operation returned.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / kind

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

addedOutput schema / properties / last_modified

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

addedOutput schema / properties / last_seen

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

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

addedOutput schema / properties / revision

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

addedOutput schema / properties / revision_count

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

addedOutput schema / properties / source_disagreements

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

addedOutput schema / properties / source_freshness

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

addedOutput schema / properties / source_id

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

addedOutput schema / properties / sources

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

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

addedOutput schema / properties / title_key

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

addedOutput schema / properties / url

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

addedOutput schema / properties / values

Added value: +{
+  "description": "The `values` 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 declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful billing context ($0.05 USDC) but the '33 fields including Accept, User-Agent' clause is opaque and doesn't clarify behavior, and it says nothing about pagination, refresh semantics, or rate limits.

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

Conciseness2/5

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

It is short, but the sizing is wasted: the sibling-differentiation is front-loaded correctly, yet the middle clause about 'an object with 33 fields including Accept, User-Agent' is noise that reads like leaked HTTP header metadata, and the pricing dangles at the end. Every sentence should earn its place; that fragment does not.

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

Completeness2/5

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

For a 7-parameter, filter-heavy query tool with an output schema and full annotations, the description should explain what the filters select (time window, category, geography, source) and the effect of refresh. Instead it covers only sibling choice and price, leaving the agent unequipped to parameterize the call correctly.

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 coverage is 100%, but the schema descriptions are generic boilerplate ('The since this operation operates on...'), so the schema itself is weak even at full coverage. The tool description adds no semantics for limit, since, until, refresh, category, geography or source_ids, leaving the agent to guess the time-window format and filter semantics. Baseline 3 applies since the schema technically documents every parameter, but nothing above baseline is earned.

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 the resource (bio outbreak events) and ties it to the OutbreakSignal service, so the agent knows what it retrieves. It is marred by a garbled trailing fragment ('an object with 33 fields including Accept, User-Agent') that muddies rather than clarifies purpose, but the core verb+resource is still identifiable.

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 the near-identical sibling: 'use it rather than `get_bio_labcyber_events` for bio outbreak events'. That is a real disambiguation rule. It stops short of describing when to call this at all (e.g. incident monitoring vs. historical pull) or what happens with no filters applied.

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.