Skip to main content
Glama

Get application configuration

get_application_configuration
Read-only

Read one section of how an Application is configured. section picks it: environments (the Application's environments and their deploy targets), operating_expectations (the availability, recovery, retention and budget expectations adopted for one environment; needs environment_id), repository_credential (the name of the Git credential the Application builds with and whether it resolves, never the credential), launch_plan (the launch plan of the Application's current contract, or of commit_sha), rollbacks (the builds one cluster can be rolled back to and the rollbacks already started there; needs cluster_id) and organisation_settings (the organisation-wide application defaults; takes no application_id). Every other section needs application_id. Read-only.

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": {
      "section": "<section>"
    },
    "name": "get_application_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesWhich section to read.
cluster_idNorollbacks only: the cluster the Application is deployed on.
commit_shaNolaunch_plan only: read the plan of this commit's contract instead of the current one.
application_idNoThe Application's id; required for every section but organisation_settings.
environment_idNooperating_expectations only: the environment's id, from the environments section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the closing "Read-only" merely restates that. It does add one genuinely useful disclosure beyond annotations: repository_credential returns only the credential's name and whether it resolves, never the credential itself, which tells the agent it is safe to call without leaking secrets. It does not describe pagination, error behavior, or what a failed credential resolution looks like, so the addition is modest.

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?

Dense but front-loaded: the action is stated first, then a single enumerative sentence gives each section's meaning, with the cross-cutting 'every other section needs application_id' rule at the end. No filler sentences, though the run-on parenthetical list is heavy to parse and could have been bulleted.

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?

With no output schema, the description carries responsibility for telling the agent what each section returns, and it does so for all six values with concrete payload descriptions (environments and deploy targets, rollbacks and already-started rollbacks, etc.). Combined with a fully documented schema and readOnly annotations, an agent has enough to call this correctly; only error and empty-result behavior is unspecified.

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 all five parameters and the enum are already documented, including the 'X only' scoping notes. The description's parentheticals restate those same mappings and add semantic meaning mostly for the enum values (what each section returns), which is helpful but overlaps heavily with the schema. 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 ("Read one section of how an Application is configured") and immediately names the discriminating parameter (section) plus all six values it can take. An agent can tell this apart from get_application and the many get_application_* siblings because the definition enumerates exactly which slices of configuration live here.

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?

Clearly explains when each section applies and what each section requires (operating_expectations needs environment_id, rollbacks needs cluster_id, organisation_settings takes no application_id), which is real routing guidance for the agent. It stops short of naming an alternative tool for configuration outside these six sections, so it is strong but not exhaustive.

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.