InterAI Risk Oracle

A2A Agent Card

oracle.agent_card

Read-onlyIdempotent

Read-only A2A Agent Card with agent identity, security scheme, capabilities, and skills. Use it when selecting or integrating InterAI through A2A; use oracle.service_descriptor for general service metadata or oracle.discovery_bundle for complete bootstrap context.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oracle.agent_card"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`skills`	Yes
`version`	Yes
`provider`	No
`security`	No
`description`	Yes
`capabilities`	Yes
`securitySchemes`	No
`documentationUrl`	No
`defaultInputModes`	No
`defaultOutputModes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "InterAI A2A Agent Card returned as machine-readable JSON.",
+  "properties": {
+    "capabilities": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "defaultInputModes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "defaultOutputModes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "description": {
+      "type": "string"
+    },
+    "documentationUrl": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "provider": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "security": {
+      "type": "array"
+    },
+    "securitySchemes": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "skills": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "description",
+    "url",
+    "version",
+    "capabilities",
+    "skills"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior3/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 description's 'Read-only' restates covered safety behavior. It adds useful context about the card's contents, but not deeper behavioral details like auth requirements, error behavior, or response semantics.

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 sentences deliver the core purpose and contextual routing without waste. The key information is front-loaded, and the sibling guidance is packed into a single clear clause.

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 a rich output schema, clear annotations, and a description that covers both content and usage alternatives, an agent has everything needed to select and invoke this tool correctly. There are no parameters to clarify and no missing safety disclosures.

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 input schema has zero parameters with 100% coverage, so there is no parameter documentation burden for the description. The zero-parameter baseline of 4 is appropriate, and no additional parameter explanation is 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 clearly states the tool is a 'Read-only A2A Agent Card' and enumerates its contents: agent identity, security scheme, capabilities, and skills. It also differentiates from sibling tools by explicitly naming oracle.service_descriptor and oracle.discovery_bundle.

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 explicitly says when to use the tool ('when selecting or integrating InterAI through A2A') and directs the agent to alternatives for related use cases: oracle.service_descriptor for general service metadata and oracle.discovery_bundle for complete bootstrap context.

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.