Skip to main content
Glama

Restore prompt

restore-prompt

Restore an archived prompt to active, so it joins the next visibility run. Refused when the workspace is at its prompt quota. Archived ids come from get-prompt-scores with status archived.

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": {
      "prompt_id": "<prompt_id>"
    },
    "name": "restore-prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
prompt_idYesPrompt ID from get-prompt-scores

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / prompt_id / description
      Previous value: -"Prompt ID"New value: +"Prompt ID from get-prompt-scores"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / prompt_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world mutation; the description adds real context beyond them by disclosing the post-condition (joins the next visibility run) and an explicit refusal condition (quota exceeded). It does not say whether existing scores/history for the prompt are retained after restore.

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?

Three short sentences, each carrying distinct information: the action and effect, the failure condition, and the id source. The action is front-loaded and nothing is redundant.

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?

For a single-parameter mutation with annotations covering the safety profile and no output schema, the description covers action, effect, precondition, and input provenance. Only minor gaps remain, such as whether restoring preserves the prompt's historical scores or how the restore interacts with an in-flight visibility run.

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?

With one parameter at 100% schema coverage the baseline is 3, but the description adds meaning the schema lacks: only ids currently in archived status are valid, and they come from get-prompt-scores filtered by status archived. That is a genuine constraint beyond the schema's 'Prompt ID from get-prompt-scores'.

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?

Specific verb (restore) plus resource (an archived prompt) with the concrete resulting state: it becomes active and joins the next visibility run. This is clearly the inverse of the sibling archive-prompt, so an agent can distinguish them without opening either 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?

States a precondition (workspace prompt quota) and points to get-prompt-scores with status archived as the source of valid ids, which tells the agent both when the call will fail and how to obtain input. It does not explicitly name archive-prompt as the inverse or say when not to restore, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources