Synthex Forge — x402 Paid Agent Services

Get Bio Labcyber Events

get_bio_labcyber_events

Read-onlyIdempotent

BioTrust Service 08 — the LabCyber Sentinel. use it rather than get_bio_outbreak_events for bio labcyber events, not bio outbreak events; an object with 31 fields including action, actor. $0.5 USDC.

Input Schema

Name	Required	Description
`config`	No	The config this operation operates on. See the schema for its type and whether it is required.
`events`	No	The events this operation operates on. See the schema for its type and whether it is required.
`allowlist`	No	The allowlist this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`ts`	No	The `ts` field of the response.
`key`	No	The `key` field of the response.
`low`	No	The `low` field of the response.
`high`	No	The `high` field of the response.
`path`	No	The `path` field of the response.
`role`	No	The `role` field of the response.
`actor`	No	The `actor` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`action`	No	The `action` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`medium`	No	The `medium` field of the response.
`mfa_ok`	No	The `mfa_ok` field of the response.
`country`	No	The `country` field of the response.
`outcome`	No	The `outcome` field of the response.
`rule_id`	No	The `rule_id` field of the response.
`event_id`	No	The `event_id` field of the response.
`findings`	No	The `findings` field of the response.
`metadata`	No	The `metadata` field of the response.
`resource`	No	The `resource` field of the response.
`severity`	No	The `severity` field of the response.
`bytes_out`	No	The `bytes_out` field of the response.
`source_ip`	No	The `source_ip` field of the response.
`timestamp`	No	The `timestamp` field of the response.
`change_ref`	No	The `change_ref` field of the response.
`by_severity`	No	The `by_severity` field of the response.
`finding_count`	No	The `finding_count` field of the response.
`suppressed_by`	No	The `suppressed_by` field of the response.
`evidence_digest`	No	The `evidence_digest` field of the response.
`evidence_event_ids`	No	The `evidence_event_ids` field of the response.
`evidence_preserved`	No	The `evidence_preserved` field of the response.
`suppressed_by_allowlist`	No	The `suppressed_by_allowlist` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 schema fields changedOct 31, 2026

addedOutput schema / properties / action

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

addedOutput schema / properties / actor

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

addedOutput schema / properties / by_severity

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

addedOutput schema / properties / bytes_out

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

addedOutput schema / properties / change_ref

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

addedOutput schema / properties / country

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

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

addedOutput schema / properties / evidence_event_ids

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

addedOutput schema / properties / evidence_preserved

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

addedOutput schema / properties / finding_count

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

addedOutput schema / properties / findings

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

addedOutput schema / properties / high

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

addedOutput schema / properties / key

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

addedOutput schema / properties / low

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

addedOutput schema / properties / medium

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

addedOutput schema / properties / metadata

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

addedOutput schema / properties / mfa_ok

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

addedOutput schema / properties / outcome

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

addedOutput schema / properties / path

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

addedOutput schema / properties / resource

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

addedOutput schema / properties / role

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

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

addedOutput schema / properties / source_ip

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

removedOutput schema / properties / status

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

addedOutput schema / properties / suppressed_by

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

addedOutput schema / properties / suppressed_by_allowlist

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

addedOutput schema / properties / timestamp

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

addedOutput schema / properties / ts

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

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

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/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 behavior. The description adds useful context beyond annotations: the tool costs $0.5 USDC and returns an object with 31 fields including action and actor. It does not discuss auth or rate limits, but cost disclosure is meaningful for a paid read.

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

Conciseness4/5

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

The description is short and front-loads the sibling distinction, but the leading branding phrase 'BioTrust Service 08 — the LabCyber Sentinel' adds little functional value and the output/cost sentences are syntactically fragmented.

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?

Given an output schema, full schema coverage, and annotations covering safety, the description provides the missing pieces an agent needs: tool selection guidance, cost, and a brief output hint. It is complete enough to call correctly, though it could say more about optional inputs or response size.

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 the three parameters. The description does not mention config, events, or allowlist at all, so it adds no parameter-level meaning beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the specific resource (bio labcyber events) and explicitly distinguishes it from the sibling `get_bio_outbreak_events`, including the exclusion 'not bio outbreak events'. An agent can tell exactly what it retrieves without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative tool (`get_bio_outbreak_events`) and the condition under which to choose this one instead, with an explicit negative case. That is clear routing guidance with no inference required.

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.