Skip to main content
Glama

Get application demo config

get_application_demo_config
Read-only

Read an Application's saved demo configuration: the env entries (name, value, secret flag) and throwaway-database flag every demo launch lane inherits (portal launches, deploy_pr_demo, SCM-webhook auto-previews). Secret entries show their ${SECRET_SLOT:} sentinel, never a resolved value. Also reports the full-stack stack profile and shared base stack the application's demos depend on, when configured - read-only context an update never touches. Read this before update_application_demo_config - the update replaces env and database wholesale.

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

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application whose demo configuration to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=true; the description goes well beyond by disclosing that secret entries surface as a ${SECRET_SLOT:<uuid>} sentinel rather than resolved values, that the env/database config is inherited across portal launches, deploy_pr_demo, and SCM-webhook auto-previews, and that stack profile data is read-only untouched 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?

Front-loaded with the core read statement, then caveats about secret sentinels and the update warning. Every clause carries information, though the middle sentence is heavily parenthetical and slightly dense for a three-sentence description.

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?

No output schema exists, so the description carries the burden of describing return contents, and it does so concretely (env entries, secret flag, throwaway-db flag, profile/base stack). For a one-parameter read tool, an agent has everything needed to call it and interpret the result.

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% and there is a single required application_id already documented in the schema, so baseline 3 applies. The description adds no extra meaning about the parameter (e.g., where to obtain the ID or behavior when it's invalid).

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?

Opens with a specific verb+resource ("Read an Application's saved demo configuration") and enumerates the exact contents returned: env entries with name/value/secret flag, the throwaway-database flag, and the stack profile/base stack. This is clearly separable from siblings like get_application, get_demo_diagnostics, or inspect_demo.

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

Usage Guidelines5/5

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

Explicitly routes usage: "Read this before update_application_demo_config - the update replaces env and database wholesale." That names the alternative tool and the condition (wholesale replacement risk) that makes reading first necessary.

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.