AgentsPodium Hosting

List platforms and plans

list_platforms

Read-only

List available AgentsPodium engines (platforms) and hosting plans (tiers), with prices and capabilities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tiers`	Yes	Available hosting plans (tiers) with prices, as published by the account API.
`engines`	Yes	Available runtime engines.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "engines": {
+      "description": "Available runtime engines.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "capabilities": {
+            "description": "Engine-specific capability flags, as published by the account API."
+          },
+          "id": {
+            "description": "Engine id (e.g. hermes).",
+            "type": "string"
+          },
+          "label": {
+            "description": "Human-readable engine name.",
+            "type": "string"
+          },
+          "minTier": {
+            "description": "Cheapest tier this engine can run on.",
+            "type": "string"
+          },
+          "status": {
+            "description": "Engine availability status (e.g. stable, beta).",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "minTier",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tiers": {
+      "description": "Available hosting plans (tiers) with prices, as published by the account API.",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "required": [
+    "engines",
+    "tiers"
+  ],
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description adds minor context by specifying that results are 'available' engines and plans with prices and capabilities, but it does not disclose additional behaviors such as whether results are static, ordered, or require authentication. The annotation coverage lowers the burden, so a middle score is appropriate.

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 a single sentence that front-loads the verb and resource, includes all key details, and contains no filler or redundant phrasing. Every word 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?

Given the tool's simplicity (no parameters, no nested objects, present output schema, and annotations covering safety), the description is complete. It clearly states what the tool returns and is sufficiently informative for an agent to invoke it correctly.

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 accepts no parameters and the schema coverage is 100%, so there is nothing for the description to explain. With zero parameters, the baseline is 4, and the description correctly does not invent unnecessary parameter details.

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 verb ('List') and resource ('AgentsPodium engines (platforms) and hosting plans (tiers)') and specifies the returned attributes ('prices and capabilities'). This clearly distinguishes the tool from the sibling list_instances, which focuses on instances rather than platform/plan catalog data.

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 description makes the context clear: this is the tool for viewing platform and plan information. It does not explicitly mention alternatives or when-not-to-use, but the contrast with siblings like create_instance and list_instances makes the usage intent obvious. No exclusions are stated, which is acceptable for a simple catalog tool.

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.