Skip to main content
Glama

Archive prompt

archive-prompt
Destructive

Archive a prompt. It leaves future visibility runs and stops counting toward the prompt quota; its past scores and answers are kept, and restore-prompt brings it back. It keeps its topic.

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": "archive-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.5/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description spells out exactly what changes and what survives: it exits future visibility runs, stops counting toward quota, keeps past scores and answers, retains its topic, and is reversible via restore-prompt. That is precisely the retention/reversibility context annotations cannot convey.

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 tight sentences, front-loaded with the action, then effects, then reversibility. Every clause carries a distinct fact (quota, visibility runs, retained history, topic retained) with no filler.

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

Completeness5/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 no output schema, the description covers the full decision surface: side effects, quota impact, data retention, topic retention, and the recovery path. Nothing an agent needs before calling it is missing.

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?

Only one parameter, and the schema already documents it fully (UUID format, pattern, and the note that the ID comes from get-prompt-scores). The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Opening sentence gives a specific verb (archive) and resource (prompt), and the description names the inverse operation, restore-prompt, which lets an agent place it precisely among siblings like restore-prompt and archive-article without opening a 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?

It gives clear decision context: archiving removes the prompt from future visibility runs and frees quota while preserving history, so an agent knows this is the soft-removal option. It stops short of explicitly naming when to prefer this over alternatives (e.g. moving topics or permanent deletion).

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