DevReply

List apps

list_apps

Read-only

The organization's apps (a secret key sees its one app): id, name, platforms, how many conversations wait on the team, and whether agents may reply.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`apps`	Yes	The apps, oldest first.
`access`	Yes	This connection's access: read or read_write.
`can_set_up_apps`	Yes	This connection may create and set up apps (an owner, read and write).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "access": {
+      "description": "This connection's access: read or read_write.",
+      "type": "string"
+    },
+    "apps": {
+      "description": "The apps, oldest first.",
+      "items": {
+        "properties": {
+          "agent_replies": {
+            "description": "What reply_to_user does here: off, draft or send.",
+            "type": "string"
+          },
+          "id": {
+            "description": "The app's id: pass it as app_id.",
+            "format": "uuid",
+            "type": "string"
+          },
+          "name": {
+            "description": "The app's name.",
+            "type": "string"
+          },
+          "platforms": {
+            "description": "Its platforms: ios, android, web.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "waiting_on_team": {
+            "description": "Open conversations whose last message is the user's.",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "can_set_up_apps": {
+      "description": "This connection may create and set up apps (an owner, read and write).",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "apps",
+    "access",
+    "can_set_up_apps"
+  ],
+  "type": "object"
+}

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/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 useful behavioral context beyond annotations: a secret key sees only its one app, and the response includes conversation queue counts and whether agents may reply. Rate limits and pagination are not mentioned, but the credential-scoping detail is valuable.

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, front-loaded sentence with no filler. It efficiently packs the resource, credential behavior, and returned fields into one compact statement.

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 zero-parameter list tool with an output schema and read-only annotations, the description covers the resource, credential-dependent visibility, and key returned fields. Usage guidance and pagination details are missing, but the output schema and annotations fill most other gaps.

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?

There are zero parameters, so the baseline is 4 per the scoring rules. The description correctly does not introduce any parameter details, and the empty schema is fully documented.

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 identifies the resource (the organization's apps) and its scope, including the credential-dependent visibility rule for secret keys. It does not explicitly state the verb 'list' in the description text (though the title does), and it does not name a sibling like get_app to differentiate use cases.

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 guidance is provided on when to use this tool versus alternatives such as get_app or create_app. The description only states what is returned, leaving the agent to infer the appropriate context.

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

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