Skip to main content
Glama

Set application operating expectations

set_application_operating_expectations
Destructive

Adopt the operating expectations of one environment of an Application: availability, data region, recovery time, tolerated data loss, retention, monthly budget and who does routine care. Every field is required, and expected_revision must be the revision last read (0 when none is adopted): a stale revision is refused so a change made meanwhile is not overwritten. Needs applications.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>",
      "environment_id": "<environment_id>",
      "expected_revision": "<expected_revision>",
      "availability_percent": "<availability_percent>",
      "data_region": "<data_region>",
      "recovery_minutes": "<recovery_minutes>",
      "data_loss_minutes": "<data_loss_minutes>",
      "retention_days": "<retention_days>",
      "monthly_budget_cents": "<monthly_budget_cents>",
      "routine_care": "<routine_care>"
    },
    "name": "set_application_operating_expectations"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_regionYesWhere the environment's data must stay.
routine_careYesHow routine care is handled.
application_idYesThe Application's id.
environment_idYesThe environment's id.
retention_daysYesHow long backups are kept, in days.
recovery_minutesYesHow long a recovery may take, in minutes.
data_loss_minutesYesHow much recent data a recovery may lose, in minutes.
expected_revisionYesThe revision the caller last read; 0 when none is adopted yet.
availability_percentYesExpected availability, in percent.
monthly_budget_centsYesThe environment's monthly budget, in cents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing an authorization requirement ('Needs applications.deploy') and, more importantly, the optimistic-concurrency contract: expected_revision must be the last-read revision and a stale revision is refused so a concurrent change is not silently overwritten. What it does not cover is the destructive side the annotations flag (destructiveHint=true) — whether adopting expectations wholly replaces any previously adopted set, and what happens to fields if the revision matches.

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?

Two sentences, front-loaded with the resource and scope, then the concurrency and permission constraints — no filler. The first sentence is dense with an eight-item list, but each item carries information.

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 ten-parameter, fully-required mutation with no output schema, the description supplies scope, all-or-nothing requiredness, concurrency handling, and permission needs. The remaining gap is behavioral: with destructiveHint=true the agent would benefit from knowing that an accepted call replaces the environment's existing expectations outright.

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 every one of the ten parameters already carries its own documented meaning, and the description's field list largely mirrors those names. The one piece of added meaning is the restatement of expected_revision semantics and '0 when none is adopted', which duplicates the schema text rather than extending it.

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?

Uses a specific verb ('Adopt') plus the exact resource ('the operating expectations of one environment of an Application') and enumerates the fields being set, so the agent knows precisely what will change. It stops short of naming a sibling tool it must not be confused with, but the field enumeration makes it distinguishable from neighbors like set_application_auto_deploy or set_cluster_variable.

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?

Implies the context (an environment of an Application that needs availability/recovery/budget expectations defined) and states the required permission 'applications.deploy', which is a real precondition. However, it never says when to prefer this over adjacent settings tools, nor any case in which it should not be used, leaving selection guidance to inference.

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.