Skip to main content
Glama
Omnidim

@omnidim-ai/mcp-server

by Omnidim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

restoreAgentVersion

Destructive

Roll back a live agent to a saved version. Current settings are backed up first, so you can undo; deleted knowledge files or integrations are skipped.

Instructions

Restore a version onto the live agent. Your current setup is saved first as a backup version, so restoring is undoable. Configuration is brought back; any knowledge files or integrations that were deleted since this version was saved can't be re-linked, and are reported in skipped. (Tags: Agents)

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe ID of the agent.
requestBodyNoThe JSON request body.
version_numberYesThe version number, as returned in `version_number` from the list or save endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • addedInput schema / properties / requestBody
      Added value: +{
+  "description": "The JSON request body.",
+  "properties": {},
+  "type": "object"
+}
  2. First observedv0.9.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds substantial value: it discloses that the current setup is auto-backed-up first so the operation is effectively reversible, and that deleted knowledge files/integrations cannot be re-linked and are surfaced in `skipped`. This meaningfully qualifies the destructive hint. It does not cover auth/permission requirements or rate limits, so not a 5.

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?

Three tight sentences that lead with the action and undoability, then the partial-failure caveat. Every sentence earns its place; only the trailing '(Tags: Agents)' is minor noise.

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?

With no output schema and 100% schema coverage, the description correctly carries the behavioral burden, including the `skipped` output field for partial re-linking failures. Reversibility and side-effect semantics are covered, though permission or rollback-scope details are left implicit.

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 agent_id and version_number are fully documented in the schema. The description adds no parameter-level meaning (e.g., version number format or requestBody purpose), so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Restore a version onto the live agent') with clear scope, distinguishing it from siblings like createAgentVersion, listAgentVersions, renameAgentVersion, and diffAgentVersion. An agent can identify this as the rollback operation without opening the schema.

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?

The description establishes the context (rolling back to a saved version) and notes that it is undoable, giving clear signals for when to use it. However, it does not explicitly name alternatives or exclusions (e.g., 'to inspect differences, use diffAgentVersion instead'), so routing depends on inference.

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