Skip to main content
Glama

Get application deployments

get_application_deployments
Read-only

Get where an Application is deployed: the clusters, namespaces, chart versions, and deployment states. 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": {
      "application_id": "<application_id>"
    },
    "name": "get_application_deployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, and 'Read-only.' merely restates it. The genuinely additive part is the enumeration of what the response contains (clusters, namespaces, chart versions, deployment states), but there is no mention of behavior for unknown application_id or of result volume/pagination.

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 front-loaded sentence covering purpose, return scope, and safety, followed by a two-word qualifier. No filler or redundancy in structure.

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, describing the returned fields is the right compensating move, and a one-parameter read tool needs little more. Only edge-case behavior (nonexistent application, empty result) is unaddressed.

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?

There is a single parameter with 100% schema description coverage ('The Application's id.'), so the schema carries the semantics. The description adds no format, sourcing, or scoping detail beyond it — baseline 3 applies.

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 gives a specific verb+resource ('Get where an Application is deployed') and enumerates the returned facets: clusters, namespaces, chart versions, and deployment states. That distinguishes it from generic siblings like get_application or get_deployments, though it never names those siblings explicitly.

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 it should call this when it needs to know where a given application lands. There is no explicit when-to-use statement, no contrast with get_deployments / get_stack_deployments, and no prerequisites or exclusions.

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.