MCP Prompt Manager

by Tae4an

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

import-prompts

Import prompts from JSON format into your prompt manager. Supports backup, duplicate handling, and metadata merging.

Instructions

Import prompts from JSON format

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": {
      "importData": "<importData>"
    },
    "name": "import-prompts"
  }
}

Input Schema

Name	Required	Description
`importData`	Yes	Import data in export format
`createBackup`	No	Create backup before import (default: true)
`mergeMetadata`	No	Merge with existing metadata (default: true)
`skipDuplicates`	No	Skip duplicate files (default: true)
`overwriteExisting`	No	Overwrite existing files (default: false)
`validateChecksums`	No	Validate file checksums (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states 'Import prompts from JSON format', omitting behavioral details like whether it creates backups, overwrites existing files, or validates checksums—all of which are crucial for an import operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but lacks structure and fails to front-load key information beyond the bare verb and resource.

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 the tool's complexity (6 parameters, nested objects, no output schema), the description is too sparse. It fails to explain return values, error handling, or import behavior, leaving the agent underinformed.

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 the description's lack of additional parameter meaning is acceptable. Baseline 3 is appropriate as the schema already documents the parameters sufficiently.

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 verb 'Import', resource 'prompts', and format 'JSON', effectively distinguishing it from sibling tools like 'export-prompts' or 'create-prompt'.

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 on when to use this tool versus alternatives like 'create-prompt' for single imports or 'export-prompts' for the reverse operation. No exclusions or contextual hints provided.

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