Skip to main content
Glama
Sign In
SkillForge

SkillForge

by CatVinci-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

restore_skill

Restore a skill to a previous version from a backup when an optimization fails. The current version is saved before overwriting, preventing data loss.

Instructions

Restore a skill from a specific backup. Current version is backed up first.

Use this when a skill optimization went wrong and you need to roll back. The current version is always saved before overwriting, so no data is lost.

Args: name: The skill identifier. timestamp: Backup timestamp (from list_backups output).

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": {
      "name": "<name>",
      "timestamp": "<timestamp>"
    },
    "name": "restore_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
timestampYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that the current version is backed up before overwriting, ensuring no data loss. With no annotations, this is valuable but doesn't cover all edge cases (e.g., invalid timestamp).

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?

Concise, well-structured with separate usage guidance and parameter descriptions. No extraneous text.

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?

Covers purpose, behavior, usage, and parameters adequately. Has output schema, so return values don't need description. Minor gap: no mention of failure scenarios.

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?

Adds meaning beyond schema: timestamp is explicitly noted as coming from list_backups output. Schema coverage is 0%, so description compensates well, but name parameter lacks format details.

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 clearly states 'Restore a skill from a specific backup' and mentions the backup-first behavior, distinguishing it from sibling tools like list_backups and delete_skill.

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

Usage Guidelines4/5

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

Provides explicit when-to-use: 'when a skill optimization went wrong and you need to roll back.' Does not state when-not-to or alternatives, but context is clear enough.

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