Universal Agents

About Universal Agents

about_universal_agents

Read-only

What Universal Agents sells (Interplay: the brain, the playbook, Living Blocks, the universal agent), how an engagement starts, and who it is for.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`source`	Yes
`summary`	Yes
`agent_may`	Yes	What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.
`provenance`	Yes
`what_we_sell`	Yes
`how_it_starts`	Yes
`who_it_is_for`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "agent_may": {
+      "additionalProperties": false,
+      "description": "What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.",
+      "properties": {
+        "label": {
+          "type": "string"
+        },
+        "level": {
+          "type": "integer"
+        },
+        "note": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "level",
+        "label",
+        "note"
+      ],
+      "type": "object"
+    },
+    "how_it_starts": {
+      "type": "string"
+    },
+    "provenance": {
+      "additionalProperties": false,
+      "properties": {
+        "accountable": {
+          "additionalProperties": false,
+          "properties": {
+            "contact": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "title",
+            "contact"
+          ],
+          "type": "object"
+        },
+        "answer_type": {
+          "enum": [
+            "product"
+          ],
+          "type": "string"
+        },
+        "authors": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "title"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "effective": {
+          "type": "string"
+        },
+        "source": {
+          "additionalProperties": false,
+          "properties": {
+            "path": {
+              "type": "string"
+            },
+            "repo": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "repo",
+            "path"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "answer_type",
+        "authors",
+        "accountable",
+        "source",
+        "effective"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "what_we_sell": {
+      "type": "string"
+    },
+    "who_it_is_for": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "summary",
+    "what_we_sell",
+    "how_it_starts",
+    "who_it_is_for",
+    "source",
+    "provenance",
+    "agent_may"
+  ],
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds scope context (the content areas it covers), but for an informational tool it doesn't need to say much more; return format is handled by the output schema.

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?

One front-loaded sentence that carries the full content scope with no filler. The parenthetical list is dense but useful, not padding.

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?

For a no-param, read-only overview tool with an output schema, the description covers what an agent needs to decide and call. Only the omission of explicit sibling routing keeps it from being complete.

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?

Zero parameters, so the baseline is 4. The description correctly indicates no input is required, and there is nothing in the schema for it to compensate for.

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 (Universal Agents) and enumerates the content covered: what it sells (Interplay, the brain, the playbook, Living Blocks, the universal agent), how an engagement starts, and who it's for. That is concrete and distinguishable from get_pricing or request_intro, though the verb is implicit rather than an explicit 'returns/describes'.

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

Usage Guidelines2/5

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

No when-to-use guidance and no routing against siblings. An agent facing answer_faq, get_pricing, and request_intro gets no rule for choosing this overview over them; the only clue is the absence of parameters.

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

All Universal Agents 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.

Resources

Need Help?