Skip to main content
Glama

Revise application setup

revise_application_setup
Destructive

Negotiate the setup Ankra proposed for an Application by changing the defaults on its deploy option contract, and commit the rewritten .ankra/ankra.yaml to the Application's setup pull-request branch. Use this for requests like '8Gi is too much, this is a demo' (database_storage), 'make it highly available' (database_instances, replicas) or 'expose it at shop.example.com' (ingress_enabled, ingress_host). Call get_application_setup_proposal first: only options the contract already declares can be changed, and every value must satisfy that option's declared type. The revision is all-or-nothing - if any requested change is refused, the proposal is left exactly as it was and the answer names each refusal and why, so never re-offer the unchanged plan as though the request had been honoured. The database ENGINE is not an option: Ankra generates PostgreSQL through the CloudNativePG operator, and swapping it means regenerating the setup rather than revising its contract. This never deploys anything - it writes one commit on the setup branch and updates the stored contract; the user still has to deploy.

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>",
      "options": "<options>"
    },
    "name": "revise_application_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsYesThe deploy options to change, as a name-to-new-default object (for example {"database_storage": "1Gi", "replicas": "3"}). Every value is a string because the deploy contract stores defaults as text. Options not named here keep their current defaults.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and destructiveHint=true; the description goes well beyond that by disclosing all-or-nothing revision semantics, that refusals are named individually and the proposal left untouched, that it writes exactly one commit plus updates the stored contract, and that it never deploys. That is precisely the mutation-behavior context an agent needs before invoking.

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 a single dense paragraph, but the operative point (negotiate/commit on setup branch) is front-loaded and each subsequent sentence — examples, prerequisite, atomicity, engine exclusion, no-deploy caveat — carries distinct information. Slightly long-winded phrasing ('so never re-offer the unchanged plan as though the request had been honoured') is the only soft spot.

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 no output schema, the description still tells the agent what the response contains (named refusals with reasons), what side effects occur (one commit, stored contract updated), and what does not happen (no deploy). Nothing critical is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description still adds value by naming concrete option keys (database_storage, replicas, ingress_host) and the constraint that only contract-declared options can change and values must satisfy each option's declared type — guidance the JSON schema cannot express.

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?

The description states a precise verb+resource pair ('Negotiate the setup Ankra proposed for an Application') and the exact mechanism: changing defaults on the deploy option contract and committing the rewritten .ankra/ankra.yaml to the setup PR branch. It clearly distinguishes this from siblings such as get_application_setup_proposal (read) and deploy_application (deploy).

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?

It gives concrete request-to-option mappings ('8Gi is too much' -> database_storage, 'make it highly available' -> database_instances/replicas, 'expose it at shop.example.com' -> ingress_enabled/ingress_host) and explicitly requires calling get_application_setup_proposal first. It also states an exclusion: the database engine is not an option and swapping it requires regenerating the setup instead.

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.