Skip to main content
Glama
Sign In
keepmyprompts-mcp

keepmyprompts-mcp

by simopet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Read a saved prompt

get_prompt
Read-only

Retrieve the full text and notes of a saved prompt by its ID. Use this after listing prompts to access the specific prompt content you need.

Instructions

Retrieve the full text of one saved prompt by its id, including any notes. Call this after list_prompts, once you know which prompt you need.

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": {
      "id": "<id>"
    },
    "name": "get_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe prompt id, as returned by list_prompts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already mark this as read-only (readOnlyHint: true) and open-world (openWorldHint: true). The description adds that notes are included and that it is a retrieve operation, but does not disclose error handling or other behavioral details. Given the simple read nature, this is acceptable but adds only limited extra context.

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 two concise sentences: the first clearly states the action and content, the second gives usage direction. It is front-loaded and every sentence earns its place with no redundancy.

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 simple single-parameter read tool with strong annotations and sibling context, this description covers the purpose, usage sequence (after list_prompts), and what is returned (full text plus notes). No output schema exists, but the return value is adequately described.

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 schema provides 100% coverage for the only parameter, id, with description 'The prompt id, as returned by list_prompts.' The tool description adds little beyond reinforcing 'by its id', so it does not significantly enhance parameter understanding beyond the schema.

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 tool retrieves the full text of one saved prompt by its id, including notes. It distinguishes from siblings by specifying it is for a single prompt and recommends calling it after list_prompts.

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 explicitly tells the agent when to use this tool: 'Call this after list_prompts, once you know which prompt you need.' This provides clear sequencing and context, though it does not explicitly mention alternatives or exclusions.

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