InterAI Risk Oracle

Discovery Bundle

oracle.discovery_bundle

Read-onlyIdempotent

Read-only bootstrap or handoff bundle with service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. Use it for complete integration context; use oracle.service_descriptor for focused service metadata, oracle.agent_card for A2A capabilities, or oracle.get_pricing for costs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`runtime`	Yes
`samples`	Yes
`service`	Yes
`discovery`	Yes
`interfaces`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Complete machine-readable InterAI integration bundle for bootstrap and handoff.",
+  "properties": {
+    "discovery": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "interfaces": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "runtime": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "samples": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "service": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "name",
+    "service",
+    "runtime",
+    "discovery",
+    "interfaces",
+    "samples"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false. The description adds value by specifying the response contents (interfaces, contracts, schemas, sample payloads) and the 'one response' nature, but does not go beyond that with additional caveats or side effects. With strong annotations, this is sufficient.

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

Conciseness5/5

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

The description is two sentences: the first front-loads the tool's core purpose and contents, the second provides routing guidance. No wasted words or repetition of schema details.

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

Completeness5/5

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

Given the tool has zero parameters and an output schema that presumably documents the response, the description covers what the agent needs: when to use it, what it returns, and how it differs from siblings. Annotations cover safety/idempotence, so nothing is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and the schema has 100% coverage, leaving no ambiguity. The description adds no parameter details because none are needed, and it correctly focuses on capabilities rather than inputs.

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 a clear purpose: a read-only bootstrap or handoff bundle that returns service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. It also names alternative sibling tools for different use cases, making it easy to distinguish from related tools.

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?

Explicit guidance is provided: use this tool for complete integration context, and use oracle.service_descriptor, oracle.agent_card, or oracle.get_pricing for more focused needs. This gives an agent clear routing rules.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InterAI Risk Oracle 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.