AgentsPodium Hosting

Set A2A peers

set_peers

Idempotent

Set the list of other A2A agents this instance is allowed to call by name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Instance (agent) id whose peer list is being set.
`peers`	Yes	Full replacement list of peer agents this instance may call (up to 20).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Instance (agent) id.
`name`	Yes	Display name.
`tier`	Yes	Hosting plan id.
`a2aUrl`	Yes	A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled.
`domain`	Yes	Customer-owned domain serving the instance, or null.
`engine`	Yes	Runtime engine id (e.g. hermes).
`status`	Yes	Lifecycle status (e.g. running, stopped).
`createdAt`	Yes	ISO timestamp when the instance was created.
`endpointUrl`	Yes	Public HTTPS endpoint for the instance, or null if not yet assigned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 8, 2026

addedInput schema / properties / id / description

Added value: +"Instance (agent) id whose peer list is being set."

addedInput schema / properties / peers / description

Added value: +"Full replacement list of peer agents this instance may call (up to 20)."

addedInput schema / properties / peers / items / properties / name / description
```
Added value: +"Name other agents use to address this peer over A2A."
```

addedInput schema / properties / peers / items / properties / token / description

Added value: +"Bearer token to send when calling this peer, if it requires one."

addedInput schema / properties / peers / items / properties / url / description
```
Added value: +"A2A JSON-RPC endpoint URL of the peer agent."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "a2aUrl": {
+      "description": "A2A JSON-RPC endpoint for the instance, or null if A2A is not enabled.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "createdAt": {
+      "description": "ISO timestamp when the instance was created.",
+      "type": "string"
+    },
+    "domain": {
+      "description": "Customer-owned domain serving the instance, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "endpointUrl": {
+      "description": "Public HTTPS endpoint for the instance, or null if not yet assigned.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "engine": {
+      "description": "Runtime engine id (e.g. hermes).",
+      "type": "string"
+    },
+    "id": {
+      "description": "Instance (agent) id.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Lifecycle status (e.g. running, stopped).",
+      "type": "string"
+    },
+    "tier": {
+      "description": "Hosting plan id.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "engine",
+    "tier",
+    "status",
+    "endpointUrl",
+    "a2aUrl",
+    "domain",
+    "createdAt"
+  ],
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already carry idempotency and open-world hints. The description adds that the operation updates call permissions and that peers are addressed by name. It doesn't restate the full-replacement behavior, but the schema's 'Full replacement list' phrase already covers that, and there is no contradiction.

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?

One sentence with no redundancy; the action and object are front-loaded. Every word earns its place.

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 two-parameter configuration tool with a complete schema and an output schema, the definition is nearly complete. It could spell out replacement semantics in prose, but the schema already declares 'Full replacement list' and maxItems, so no critical invocation detail is missing.

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 coverage is 100%, with meaningful descriptions for id, peers, name, url, and token. The description's 'by name' phrasing reinforces the role of the name property but adds no parameter-specific detail beyond what the schema already provides.

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 action ('Set the list') and a precise resource ('other A2A agents this instance is allowed to call by name'). This clearly distinguishes it from lifecycle and key-management siblings, so an agent can identify when this tool applies.

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

Usage Guidelines4/5

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

The sentence makes the intended use clear: configuring an instance's allowed A2A peer agents. It doesn't explicitly name alternatives or exclusions, but no sibling tool overlaps with peer-list configuration, so the context is sufficient.

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

All AgentsPodium Hosting 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.