Skip to main content
Glama

Back Up File

backup_file

Copy a file to a timestamped sibling backup without overwriting existing backups, preventing data loss when saving changes.

Instructions

Copy a file to a timestamped sibling backup without overwriting existing backups.

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": {
      "path": "<path>"
    },
    "name": "backup_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path
suffixNoBackup suffix

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the bar is lower. The description usefully explains the non-idempotency (timestamped names) and the no-overwrite guarantee, but omits error behavior for a missing source file, required permissions, and where exactly the sibling is written.

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?

A single sentence with zero filler, front-loading the action and immediately qualifying it with the non-overwrite guarantee. Nothing is redundant.

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

Completeness3/5

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

For a two-parameter copy tool with no output schema and full schema coverage, the essentials are present, but failure modes (source missing, backup name collision) and the return value/behavior contract remain unaddressed. Adequate but with clear gaps.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The mention of a timestamped sibling loosely relates to the optional suffix parameter but does not clarify its format or effect, adding little beyond the schema.

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 gives a specific verb and resource ("Copy a file") plus the destination concept ("timestamped sibling backup"), which lets an agent distinguish it from write_file or delete_file. It stops short of explicitly naming the sibling it replaces, so differentiation is inferred rather than stated.

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?

Usage is only implied: the phrase "without overwriting existing backups" hints at when to prefer this over write_file, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer the selection criteria.

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