InterAI Risk Oracle

Service Descriptor

oracle.service_descriptor

Read-onlyIdempotent

Read-only general service descriptor with identity, endpoints, billing, trust, and supported agent protocols. Use it to inspect service-level integration metadata; use oracle.agent_card for A2A skills or oracle.discovery_bundle for the complete bootstrap package.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`billing`	Yes
`version`	Yes
`discovery`	Yes
`endpoints`	Yes
`description`	Yes
`agent_protocols`	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": "Focused InterAI service-level metadata covering identity, endpoints, billing, trust, and agent protocols.",
+  "properties": {
+    "agent_protocols": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "billing": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "description": {
+      "type": "string"
+    },
+    "discovery": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "endpoints": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "id",
+    "version",
+    "description",
+    "discovery",
+    "endpoints",
+    "billing",
+    "agent_protocols"
+  ],
+  "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 destructiveHint=false, so the safety profile is fully covered. The description adds value beyond annotations by revealing the descriptor's internal contents (identity, endpoints, billing, trust, agent protocols), giving the agent a sense of what to expect. Clear read-only framing reinforces, not contradicts, the annotations.

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?

Two tight sentences with zero filler. The first sentence front-loads the core purpose and content scope; the second provides routing guidance. Every sentence earns its place.

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?

For a no-parameter, read-only tool with an output schema and comprehensive annotations, the description covers everything an agent needs: what it is, what it contains, when to use it, and which siblings to choose instead. Nothing essential 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 0 parameters, so per the baseline for zero-parameter tools, the description isn't obligated to document parameters. It adds value by foreshadowing the output domains (identity, endpoints, billing, trust, protocols) even though no parameter details are needed.

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 specific purpose: a general service descriptor containing identity, endpoints, billing, trust, and supported agent protocols. It explicitly distinguishes itself from oracle.agent_card and oracle.discovery_bundle, so an agent can tell this tool apart from its siblings without inspecting schemas.

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?

The description gives explicit routing: use this for service-level integration metadata, use oracle.agent_card for A2A skills, and oracle.discovery_bundle for the complete bootstrap package. Both the when-to-use and the when-not-to conditions are named with concrete sibling alternatives.

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.