Skip to main content
Glama

📋 Overview

Refine Prompt is an intelligent prompt engineering tool that transforms ordinary prompts into powerful, structured instructions for any large language model (LLM). Using Claude's advanced capabilities, it enhances your prompts to produce exceptional results across all AI platforms.

🔑 Important: Your prompt must include the keyword "refine" to activate the enhancement process.

Example: "refine, Create a function that calculates the factorial of a number"


Related MCP server: prompte-mcp

🚀 Installation

📦 Via NPM

npm install refine-prompt

🛠️ Via Smithery

You can install this MCP server directly through Smithery by visiting: Smithery - Refine Prompt

📁 Via Local Repository

# Clone the repository
git clone https://github.com/felippefarias/refine-prompt.git
cd refine-prompt

# Install dependencies
npm install

🏁 Getting Started

🔑 API Key Setup

Refine Prompt requires an Anthropic API key to access Claude's advanced capabilities:

export ANTHROPIC_API_KEY=your_anthropic_api_key

Without an API key, the tool will display an error message.

⚙️ Running the Server

npm start

Or with MCP Inspector:

npx @modelcontextprotocol/inspector npm start

🔧 Tool: rewrite_prompt - The Power of Refinement

Transform your ideas into expertly crafted prompts. This powerful tool analyzes your input and generates a professionally engineered prompt that maximizes AI understanding and response quality.

📝 Parameters

Parameter

Description

Required

prompt

Your raw prompt that needs refinement (must include "refine" keyword)

language

For code-related prompts, specify the target programming language

📋 Example Usage

{
  "name": "rewrite_prompt",
  "arguments": {
    "prompt": "refine, Summarize the main points of the article titled \"The Future of AI\""
  }
}
{
  "name": "rewrite_prompt",
  "arguments": {
    "prompt": "refine, Create a function to convert temperature between Celsius and Fahrenheit",
    "language": "typescript"
  }
}

🧠 How It Works

The server uses Claude 3 Sonnet by Anthropic to intelligently rewrite your prompts for better results. Every prompt must include the keyword "refine" to trigger the enhancement process.

It enhances your prompt by:

  1. 📐 Adding clear structure and context

  2. 📝 Specifying requirements and expectations

  3. 🔍 Including domain-specific considerations

  4. 🌐 Optimizing for any LLM understanding


✨ Features

Feature

Description

🤖 AI-Powered Refinement

Leverages Claude 3.5 Sonnet's advanced capabilities to transform your prompts

🔑 Activation with Keywords

Simply include "refine" in your prompt to trigger the enhancement

🌐 Universal Compatibility

Optimizes prompts for any type of task or domain

💻 Code-Specific Intelligence

Provides specialized enhancements for programming tasks when language is specified

🔄 Seamless Integration

Works flawlessly with any LLM-powered application or workflow

🎯 Precision-Focused

Uses 0.2 temperature setting to ensure reliable, consistent output quality

📊 Structural Clarity

Adds logical organization, clear instructions, and proper formatting


⚙️ Configuration

🖥️ Usage with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "refine-prompt": {
      "command": "npx",
      "args": [
        "-y",
        "refine-prompt"
      ]
    }
  }
}
# Clone the repository
git clone https://github.com/felippefarias/refine-prompt.git
cd refine-prompt

# Install dependencies
npm install

# Run the server
node index.js

📊 Examples

📝 General Prompt Enhancement

refine, Summarize the main points of the article titled "The Future of AI"
{
  "prompt": "refine, Summarize the main points of the article titled \"The Future of AI\""
}
refine, Create a function that sorts an array of objects by a specific property
{
  "prompt": "refine, Create a function that sorts an array of objects by a specific property",
  "language": "typescript"
}

The tool will rewrite both prompts to be more structured and detailed for optimal results with any LLM.


🚀 Elevate Your AI Interactions

Refine Prompt bridges the gap between human thinking and AI understanding. By transforming your natural language instructions into expertly engineered prompts, it helps you unlock the full potential of any language model. Whether you're a developer, content creator, researcher, or AI enthusiast, Refine Prompt gives you the power to communicate with AI more effectively.


📄 License

Refine Prompt is licensed under the MIT License. You are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

1 tool
refine_promptA

This tool MUST be used whenever a user asks to refine, rewrite, improve, enhance, or optimize a prompt. It transforms raw prompts into more effective versions that are clearer, more detailed, and better structured to improve results from Large Language Models (LLMs). When users mention 'refine prompt' or similar phrases, use this tool.

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYesThe raw user prompt that needs rewriting.
languageNoOptional: The primary programming language if the prompt is code-related (e.g., typescript, python). Helps tailor coding prompts.

TDQS

A4/5.0
Behavior3/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 of behavioral disclosure. It describes the tool's function and transformation process but lacks details on behavioral traits such as rate limits, error handling, or output format. The description doesn't contradict annotations (none exist), but it provides only basic operational context without deeper behavioral insights.

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 appropriately sized and front-loaded, with the core purpose stated in the first sentence. Each sentence adds value: the first defines the tool's function, the second explains the transformation, and the third provides usage triggers. There's minimal redundancy, though it could be slightly more concise by combining some phrases without losing clarity.

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 moderate complexity (2 parameters, no output schema, no annotations), the description covers purpose and usage well but lacks details on behavioral aspects and output. It doesn't explain what the refined prompt looks like or any constraints, which would be helpful since no output schema exists. This makes it adequate but with gaps in completeness for an agent's full understanding.

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 input schema already documents both parameters thoroughly. The description doesn't add any additional meaning or context beyond what the schema provides (e.g., no examples, edge cases, or usage tips for parameters). This meets the baseline score of 3, as the schema handles parameter documentation adequately.

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's purpose with specific verbs ('refine, rewrite, improve, enhance, or optimize a prompt') and identifies the resource ('prompt'). It explicitly distinguishes what the tool does ('transforms raw prompts into more effective versions') and how it achieves this ('clearer, more detailed, and better structured to improve results from LLMs'). No siblings exist, but the description is comprehensive and unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit usage guidelines with clear triggers ('whenever a user asks to refine, rewrite, improve, enhance, or optimize a prompt') and specific phrases to watch for ('refine prompt' or similar phrases). It directly states 'MUST be used' for these cases, offering definitive when-to-use instructions. Since no sibling tools exist, no alternative guidance is needed, making this complete for the context.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.2.0
    • First observedrefine_prompt

TDQS

A3.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name 'refine_prompt' follows a consistent verb_noun pattern, and there are no other tools to create inconsistency.

Tool Count2/5

A single tool feels thin for a server named 'Refine Prompt', as it suggests a narrow scope with no additional functionality like versioning, history, or batch processing. This is borderline too few for a dedicated server.

Completeness3/5

The tool covers the core action of refining prompts, but there are notable gaps such as no ability to list, retrieve, or manage previous refinements, which limits workflow completeness for a prompt refinement domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    An MCP server that transforms vague prompts into platform-optimized prompts for 58 AI platforms across 7 categories. Send a raw prompt. Get back a version specifically optimized for Midjourney, DALL-E, Sora, Runway, ElevenLabs, Claude, ChatGPT, or any of the 58 supported platforms — with the right syntax, parameters, and structure each platform expects.
    23
    160
    12
    Apache 2.0
  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that automatically enhances user prompts by applying advanced engineering techniques like chain-of-thought and few-shot reasoning based on identified intent. It optimizes technique selection through local learning and integrates directly into Claude sessions to improve output quality without additional API costs.
    6
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    An MCP server for deterministic prompt optimization in Claude Code. Score prompts across 7 quality dimensions, auto-select from 11 Anthropic techniques, and return a structural scaffold.
    1
    24
    2
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FelippeFarias/refine-prompt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server