MCP Prompt Manager

Overview Schema Source Related Servers Discussions Admin

compare-prompt-versions

Compare two versions of a prompt to see changes and differences. Identify modifications between source and target versions.

Instructions

Compare two versions of a prompt and show differences

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": {
      "filename": "<filename>",
      "fromVersion": "<fromVersion>",
      "toVersion": "<toVersion>"
    },
    "name": "compare-prompt-versions"
  }
}

Input Schema

Name	Required	Description
`filename`	Yes	The filename of the prompt to compare
`toVersion`	Yes	The target version number to compare to
`fromVersion`	Yes	The source version number to compare from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the basic action and output, omitting important details such as whether the operation is read-only, what format the differences are returned in, or any side effects. This is insufficient for an agent to fully understand the tool's behavior.

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?

The description is a single concise sentence that front-loads the purpose. It has no redundant words. However, it could be expanded to include more context without becoming verbose, but as is, it is appropriately concise for a simple tool.

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?

Given that the tool has three required parameters and no output schema, the description lacks details about the output format (e.g., diff text, structured object) and any constraints. The description is too minimal to be considered complete for an AI agent to use without additional inference.

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?

The input schema has 100% description coverage for all three parameters, each clearly explained (filename, fromVersion, toVersion). The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 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?

The description clearly states the action ('compare') and the resource ('two versions of a prompt') and indicates the output ('show differences'). It distinguishes from sibling tools like list-prompt-versions (which lists versions) and get-prompt-version (which retrieves a single version).

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 provided on when to use this tool versus alternatives such as list-prompt-versions or get-prompt-version. There is no mention of prerequisites, limitations, or when not to use it.

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