Skip to main content
Glama

List Clerk applications

list_applications
Read-onlyIdempotent

List the applications in the connected workspace (like clerk apps list). Returns data, where each application has its application_id, name, and instances with their instance_id, environment_type, and publishable_key. Secret keys are not included.

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_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "data": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "application_id": {
      +            "type": "string"
      +          },
      +          "instances": {
      +            "items": {
      +              "additionalProperties": {},
      +              "properties": {
      +                "environment_type": {
      +                  "description": "\"development\" or \"production\".",
      +                  "type": "string"
      +                },
      +                "instance_id": {
      +                  "type": "string"
      +                },
      +                "publishable_key": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "instance_id",
      +                "environment_type"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "application_id",
      +          "name",
      +          "instances"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "data"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real value beyond them: the shape of each returned record and the explicit note that secret keys are excluded, which tells the agent what it cannot retrieve from this call.

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?

Two sentences, front-loaded with the action and scope before the return detail. The return-field inventory is slightly redundant given an output schema exists, but the security note about secret keys justifies its presence.

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 read tool with full annotations and an output schema, the definition covers what it does, where it reads from, and what is withheld. Only the missing discrimination from `list_native_applications` keeps it from being fully complete.

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 no parameters and the schema coverage is 100%, so there is nothing for the description to disambiguate. The baseline of 4 applies for a zero-parameter tool.

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?

States a specific verb and resource ("List the applications in the connected workspace") and anchors it to a familiar CLI equivalent (`clerk apps list`). It does not explicitly distinguish itself from the sibling `list_native_applications`, which is the one nearby name an agent could confuse it with.

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

Usage Guidelines3/5

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

Usage is only implied by "in the connected workspace" — there are no stated preconditions, no when-not-to-use guidance, and no routing to alternatives such as `get_application` for a single record or `list_native_applications` for the other list flavor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources