Skip to main content
Glama

Move prompt to topic

move-prompt-to-topic
Destructive

Move a prompt to another topic of the same domain. Its text, scores and history stay as they are; topic-level scores reflect the change from then on. topic_id comes from list-prompt-topics.

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>",
      "topic_id": "<topic_id>"
    },
    "name": "move-prompt-to-topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topic_idYesTopic ID from list-prompt-topics, same domain
prompt_idYesPrompt ID from get-prompt-scores

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / prompt_id / description
      Previous value: -"Prompt ID"New value: +"Prompt ID from get-prompt-scores"
    • changedInput schema / properties / topic_id / description
      Previous value: -"Target topic ID"New value: +"Topic ID from list-prompt-topics, same domain"
  2. Changed3 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)$"
    • addedInput schema / properties / topic_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.2/5.0
Behavior4/5

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

Annotations already declare a non-read-only, destructive mutation, and the description adds meaningful context: prompt text, scores, and history are preserved, while topic-level scores change from then on. It does not cover permissions or reversibility, but it adds substantive behavioral detail beyond the annotations.

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, front-loaded with the action and the preservation behavior. Every sentence contributes useful information with no filler.

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 two-parameter mutation, annotations carry the safety profile, the schema fully documents parameters, and the description explains data preservation and scoring effects. Return value and reversibility are not described, which is a minor gap but not enough to make the tool unusable.

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 description coverage is 100%, and both UUID parameters are already documented in the schema, including their source tools. The description repeats that topic_id comes from list-prompt-topics but adds no syntax or format detail beyond the schema, so 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?

States a specific verb and resource ('Move a prompt to another topic') plus a key scope constraint ('same domain'). This clearly distinguishes it from sibling topic-management tools such as update-prompt-topic, list-prompt-topics, and create-prompt-topic.

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?

Gives the prerequisite that topic_id comes from list-prompt-topics and constrains moves to topics in the same domain. It does not explicitly compare against update-prompt-topic or state when not to use this tool, so it is clear but not fully exclusive.

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