agentView

List Organizations

list_organizations

Read-onlyIdempotent

Returns all organizations the authenticated user belongs to with their role, display count, member count and allocated slots. Use this to answer questions about the user's organizations, how many displays an organization has, or team membership. Requires authentication with at least content_only scope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`access_token`	No	Optional bearer token; prefer session_request_id.
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`organizations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / session_request_id

Added value: +{
+  "description": "Session handle from create_auth_session; pass it on every authenticated call.",
+  "type": "string"
+}

Changed1 schema field changedJul 6, 2026

changedInput schema / properties / access_token / description

Previous value: -"Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your identity server-side. Use access_token only when you hold an OAuth bearer token and your MCP client cannot send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional bearer token; prefer session_request_id."

Changed11 schema fields changedJun 2, 2026
- changedOutput schema / properties / count / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / allocatedSlots / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / displayCount / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / isActive / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / memberCount / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / orgId / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / plan / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / properties / role / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / organizations / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / organizations / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```

Changed1 schema field changedMay 30, 2026

changedInput schema / properties / access_token / description

Previous value: -"Optional JWT access token for authentication. Pass the token returned by get_auth_session when your MCP client does not send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your identity server-side. Use access_token only when you hold an OAuth bearer token and your MCP client cannot send it as an Authorization: Bearer HTTP header automatically."

Changed3 schema fields changedMay 23, 2026

removedInput schema / properties / access_token / default
```
Removed value: -null
```

changedInput schema / properties / access_token / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "organizations": {
+      "items": {
+        "properties": {
+          "allocatedSlots": {
+            "type": "integer"
+          },
+          "displayCount": {
+            "type": "integer"
+          },
+          "isActive": {
+            "type": "boolean"
+          },
+          "memberCount": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "orgId": {
+            "type": "string"
+          },
+          "plan": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond annotations by specifying the required authentication scope ('content_only') and the exact shape of the result set. This helps the agent understand prerequisites and output contents without over-explaining.

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 two sentences with no filler: the primary behavior is front-loaded, followed by concrete use cases and the authentication requirement. Every sentence 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?

For a read-only listing tool with a rich output schema and complete parameter descriptions, the description provides the essential missing context: what the tool returns, when to use it, and what auth is required. Nothing critical is left unstated.

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 description coverage is 100%, so both parameters are already well documented in the input schema. The description does not add extra parameter-level detail, but it doesn't need to; the baseline of 3 applies because the schema carries the semantic weight.

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 and resource ('Returns all organizations the authenticated user belongs to') and enumerates the returned fields (role, display count, member count, allocated slots). This clearly distinguishes it from singular-fetch tools like get_organization and from other list tools focused on different resources.

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 explicitly names concrete use cases: answering questions about the user's organizations, display counts, and team membership. It does not provide explicit when-not-to-use guidance or name alternative tools, but the intended context is clear enough for an agent to route correctly.

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

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