Skip to main content
Glama

ai_modeling_project_restore

Restore a selected project history version to roll back changes and recover a prior project state.

Instructions

Restore a selected project history version.

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": {
      "project_id": "<project_id>",
      "operator_id": "<operator_id>"
    },
    "name": "ai_modeling_project_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
operator_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description need only add context — but it does not say whether restoring creates a new history entry or overwrites the current state, what happens to uncommitted changes, or what permissions are required. For a mutation operation of a versioned resource, 'restore' is the exact term whose semantics (reversible? additive? rollback?) need spelling out, and the description provides none.

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

Conciseness3/5

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

One short, front-loaded sentence with no wasted words, but this is brevity by omission rather than by discipline — the length reflects missing content (version targeting, mutation semantics) rather than efficient communication.

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

Completeness2/5

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

A destructive-capable mutation on versioned project data with no output schema, no parameter documentation, and no annotations covering reversibility leaves significant unknowns. An agent cannot tell from this definition what will be restored, how the target version is chosen, or what it gets back.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning; instead it mentions neither project_id nor operator_id. Worse, 'selected project history version' implies a version argument that does not exist in the schema, which could actively confuse an agent about which parameter designates the version to restore.

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

Purpose3/5

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

The verb 'restore' and resource 'project history version' are specific enough to distinguish this from siblings like ai_modeling_project_history or ai_modeling_project_delete. However, 'selected' is left undefined, and the schema has no version selector — only project_id and operator_id — so it is unclear what 'selected' refers to or how the target version is designated.

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?

No guidance is given on when to restore versus inspect history first (ai_modeling_project_history / ai_modeling_project_history_check) or how this differs from edit. The single sentence provides no preconditions, no mention of prerequisites, and no exclusions.

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