Skip to main content
Glama

create_backup_account

Creates a backup account in 1Panel v1 to configure backup storage type, name, variables, and default status for managing server backups.

Instructions

Create backup account

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": {
      "type": "<type>",
      "name": "<name>",
      "vars": "<vars>"
    },
    "name": "create_backup_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeYes
varsYes
isDefaultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden — and it discloses nothing. It does not say whether this requires credentials, what the different 'type' values imply, what happens if a duplicate name exists, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words is short, but this is under-specification rather than conciseness; there is no front-loaded actionable content beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with three required parameters, an undocumented nested object, and zero annotation or output-schema support, the definition is completely inadequate.

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

Parameters1/5

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

Schema description coverage is 0% across 4 parameters, including a required nested 'vars' object and a required 'type' with no enumeration. The description adds no meaning to any of them, leaving the agent unable to construct a valid payload.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a verbatim restatement of the tool name with no additional information about what a 'backup account' is or what creating one entails. It is a tautology, not a clarification, and does nothing to separate it from siblings like create_backup or create_snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to create a backup account versus using update_backup_account, check_backup_account, or create_backup directly. The agent must infer the entire workflow from the sibling list alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools