Skip to main content
Glama

Set application database backup

set_application_database_backup
Destructive

Turn an Application's database-backup default on or off: whether a deploy of it arms scheduled backups of its database. It changes what the next deploy does, not the protection of a stack already deployed (protect_stack and unprotect_stack do that). Needs backups.manage.

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>",
      "enabled": "<enabled>"
    },
    "name": "set_application_database_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue arms the default, false turns it off.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description earns its keep by scoping the blast radius: nothing already deployed is affected, only future deploys. It also discloses the required permission scope. It does not address the tension with idempotentHint=false, since a boolean set-to-value reads as idempotent, but nothing in the text contradicts the annotations.

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?

Two sentences plus a short permission clause, with the core action front-loaded and the disambiguation second. Every clause carries information an agent needs; there is no restatement of the title or the schema.

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?

For a two-parameter boolean toggle with full schema coverage and no output schema, the definition supplies effect scope, non-effects, the alternative tool, and the auth requirement. Nothing an agent needs in order to select and invoke it correctly is missing.

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%, with both parameters documented inline, so the baseline is 3. The description reinforces the meaning of `enabled` behaviorally (arming the default for the next deploy) but adds no format, default, or edge-case detail beyond the schema.

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?

"Turn an Application's database-backup default on or off" is a concrete verb plus a precisely scoped resource, and the following clause ("whether a deploy of it arms scheduled backups of its database") removes the ambiguity of what a "default" means. It also names the sibling tools that handle the adjacent job, so the agent can separate this from protect_stack/unprotect_stack without opening a schema.

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?

The description states both the use case and the exclusion explicitly: it changes what the next deploy does, not the protection of an already-deployed stack, and it points at protect_stack and unprotect_stack for that case. It adds a concrete prerequisite ("Needs backups.manage"), so an agent knows whether it can even call it.

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.