MCP Prompt Manager

by Tae4an

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

favorite-prompt

Manage prompt favorites by adding or removing prompts using filename. Keep favorite prompts organized for quick access.

Instructions

Add or remove a prompt from favorites

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>",
      "action": "<action>"
    },
    "name": "favorite-prompt"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes	Action to perform: add to favorites or remove from favorites
`filename`	Yes	The filename of the prompt to favorite/unfavorite

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

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 must carry the burden. It fails to disclose what happens if already favorited (idempotent or error?), auth requirements, or side effects like notifications. Minimal disclosure.

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, focused sentence with no wasted words. It is appropriately sized and 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 no output schema and simple parameters, the description is adequate but leaves questions about return value, error handling, and behavior when prompt doesn't exist. More context 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 coverage is 100% and both parameters are described. The description adds no extra meaning beyond the schema's enumeration and filename reference, achieving baseline 3.

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 uses a specific verb ('Add or remove') and resource ('a prompt from favorites'), clearly stating the dual action. It distinguishes from sibling tools like 'list-favorites' (listing only) and 'create-prompt' (creation).

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?

The implied usage is for adding/removing favorites, but no explicit guidance on when to use vs siblings (e.g., 'list-favorites' for viewing), nor any exclusion conditions or prerequisites.

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