Skip to main content
Glama

Get application auto deploy

get_application_auto_deploy
Read-only

Read an Application's push-to-deploy switch, together with the newest build the platform observed on its tracked branch. The observed build rides along because the switch on its own does not answer the question this is consulted for: it distinguishes auto-deploy that is off from auto-deploy that is on and has had nothing to pick up. 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_auto_deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the closing "Read-only" adds nothing, but the description does disclose substantive behavior: the response bundles the newest observed build on the tracked branch and explains why that pairing is necessary to interpret the switch state. No mention of permission requirements or what happens when the branch has never been observed, which would have completed the picture.

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?

It is front-loaded with the action and return payload, and the middle sentence, though dense with a colon and a subordinate clause, carries real information about why the build is included. The trailing "Read-only" duplicates the annotation and is dead weight in an otherwise tight definition.

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?

With one parameter, full schema coverage, readOnly annotation, and no output schema, the description needs to explain what comes back and it does: the switch plus the newest observed build. An agent can call this and interpret the result without further context.

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 is documented there as "The Application's id." The description only refers generically to "an Application" and adds no format, sourcing, or lookup guidance for the parameter, so the 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 opens with a specific verb and resource: "Read an Application's push-to-deploy switch, together with the newest build the platform observed on its tracked branch." That is unambiguous and goes beyond the title by naming the second piece of returned data. It stops short of naming the sibling it complements (set_application_auto_deploy) or distinguishing itself from get_application, so sibling differentiation is left to the tool name.

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?

It states the decision the tool is consulted for: distinguishing auto-deploy that is off from auto-deploy that is on with nothing to pick up. That is clear when-to-use context rather than mere restatement. It gives no explicit when-not or named alternative for changing the switch, which keeps it below a 5.

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.