mcp

List regions

list_regions

Read-onlyIdempotent

Lists available regions.

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": "list_regions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`mode`	No
`next`	No
`error`	No
`status`	No
`details`	No
`message`	No
`regions`	No
`recovery`	No
`validation`	No
`account_notices`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 5, 2026
- addedOutput schema / properties / details
```
Added value: +{}
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / recovery
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / validation
```
Added value: +{}
```

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / account_notices

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "dismissible": {
+        "type": "boolean"
+      },
+      "id": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "message",
+      "url",
+      "dismissible"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedJun 11, 2026
- addedOutput schema / properties / next
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJun 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "mode": {
+      "type": "string"
+    },
+    "regions": {
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJun 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note that the region catalog is dynamic (openWorld) and may change, no indication of whether results are cached or account-scoped. With annotations doing all the work, the description contributes no extra behavioral context.

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?

A single short sentence that is front-loaded and wastes no words. It is arguably too thin rather than bloated, but there is no filler or redundancy to penalize.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the description need not explain return values, and a zero-parameter list tool is inherently simple. Still, it omits the one thing an agent would find valuable: that these region identifiers are the inputs other provisioning tools expect.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema is self-explanatory.

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 a specific verb (Lists) and resource (available regions), so an agent can tell it apart from the many create_*/delete_*/get_* siblings. It stops short of explaining what a 'region' means in this platform or how it relates to other resources, but the core purpose is unambiguous.

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?

There is no when-to-use guidance at all — nothing says regions are the prerequisite input for create_instance, create_database, or list_flavors/image selection. The agent must infer the workflow entirely from the tool name and the surrounding sibling names.

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

All mcp 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?