Skip to main content
Glama
Sign In
MCP Prompt Manager

MCP Prompt Manager

by Tae4an
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get-prompt-version

Retrieve the exact content of a prompt version by specifying its filename and version number.

Instructions

Get the content of a specific version of a prompt

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>",
      "version": "<version>"
    },
    "name": "get-prompt-version"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesThe version number to retrieve
filenameYesThe filename of the prompt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether the operation is read-only, requires authentication, or has rate limits. The simple statement 'Get the content' implies a read operation but offers no explicit safety guarantees.

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?

The description is a single sentence of 10 words, with zero waste. Essential information is front-loaded.

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

Completeness3/5

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

Given the tool's simplicity (2 params, no output schema), the description is adequate but minimal. It does not specify what the 'content' entails (e.g., raw text, metadata) or error handling. With many sibling tools, more context on when to choose this over others would improve completeness.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's 'The version number to retrieve' and 'The filename of the prompt'. It does not clarify version formatting or filename patterns.

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 'Get the content of a specific version of a prompt' clearly states the verb (get) and resource (content of a specific version of a prompt). It distinguishes from siblings like list-prompt-versions (which lists versions) and compare-prompt-versions (which compares versions).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The usage is implied: when you need the content of a particular prompt version. No exclusion criteria or contextual advice is provided.

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