Skip to main content
Glama

Get application

get_application
Read-only

Get one Application's details: repository coordinates, branch, chart and deployment summary, and current state. 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"
  }
}

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?

The readOnlyHint annotation already declares the safety profile, and the description's 'Read-only' is largely redundant. It adds useful context by naming the categories of data returned, but does not cover error behavior, permissions, or response shape.

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?

A single front-loaded sentence with no wasted wording. The field list is compact and the read-only note, while redundant with annotations, is brief.

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 simple single-resource read tool with complete schema coverage and a readOnlyHint annotation, the description is largely complete. It lists the main returned details, though it could say more about what 'current state' includes or how missing applications are handled.

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 the single application_id parameter is documented in the schema. The description adds no additional meaning about the identifier format or constraints, so the baseline of 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?

States a specific verb and resource: 'Get one Application's details,' and enumerates the returned content (repository coordinates, branch, chart, deployment summary, current state). It is clearly distinct from list_applications, but it does not explicitly distinguish itself from specialized siblings such as get_application_deployments or get_application_timeline.

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?

The phrase 'Get one Application's details' implies usage when a single application's overview is needed, but there is no explicit when-to-use guidance, no exclusions, and no routing to the many get_application_* alternatives.

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.