Skip to main content
Glama

Get Clerk application

get_application
Read-onlyIdempotent

Get one application in the connected workspace: its application_id, name, and instances with their instance_id, environment_type, and publishable_key. Secret keys are not included.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "get_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
nameYes
instancesYes
application_idYes

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": {
      +    "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"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low. The description still adds real value beyond them by specifying exactly which fields come back and explicitly noting "Secret keys are not included" — a security-relevant disclosure an agent could not get from annotations. It stops short of describing not-found or error behavior.

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?

One sentence, front-loaded with the action and scope, followed by the return-field list and the secret-key caveat. Every clause carries information; nothing is redundant with the name or title.

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 single-parameter read tool with an output schema and full annotation coverage, the description is nearly sufficient — purpose, return shape, and the secret-key exclusion are all covered. The only gap is behavior when the application_id is invalid or absent from the workspace.

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 coverage is 100% and the single application_id parameter already carries its format hint (app_…). The description adds no further meaning such as format validation, alternate identifiers, or lookup failure semantics, so baseline 3 applies.

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?

States a specific verb and resource ("Get one application in the connected workspace") and enumerates the returned fields (application_id, name, instances with instance_id, environment_type, publishable_key). The singular "one application" clearly distinguishes it from the list_applications sibling without needing to name it.

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: an agent can infer this is the single-record fetch when the application_id is already known. There is no explicit guidance on when to use this versus list_applications or update_application, and no stated preconditions (e.g., that the ID must exist in the connected workspace).

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