Skip to main content
Glama
nmelo

Prompt Refiner MCP Server

by nmelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DISABLE_PROGRESS_LOGGINGNoDisable colored stderr output

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
promptrefinerA

A tool for systematically refining vague ideas into well-structured prompts.

This tool helps you work with users to transform rough ideas into clear, actionable prompts through a structured clarification process.

Workflow:

  1. START: Submit the user's original idea

  2. CLARIFY: Ask the user questions and submit clarifications for key aspects:

    • purpose: What is this for? What problem does it solve?

    • audience: Who will use this? What's their skill level?

    • constraints: What are the requirements, limitations, or technical constraints?

    • context: Where/when/how will this be used? What environment?

    • success: How will success be measured? What does "done" look like?

    • scope: What's included? What's explicitly out of scope?

    • style: What tone, format, or style is needed?

  3. EXPORT: When refinement is complete, export using a template

Key aspects to explore (ask about these):

  • purpose (critical)

  • audience (critical)

  • constraints (important)

  • context (important)

  • success (important)

  • scope (helpful)

  • style (optional)

You decide what questions to ask based on what's unclear in the idea. You decide when enough clarification has been gathered. The tool just tracks your refinement steps and formats the output.

Available export templates:

  • "detailed-structured": Comprehensive with sections (Purpose, Audience, Requirements, etc.)

  • "concise-bullets": Brief bullet-point format

  • "technical-spec": Formal specification style

  • "conversational": Natural language paragraph

  • "minimal": Just the essentials

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

The single tool name 'promptrefiner' is clear and descriptive. While it doesn't follow a verb_noun pattern, consistency is trivially maintained with only one tool.

Tool Count3/5

The server has exactly one tool, which feels thin. However, the tool's purpose is narrowly scoped (prompt refinement), and the single tool encapsulates a complete workflow, making the count borderline but not extreme.

Completeness4/5

The tool covers the full prompt refinement lifecycle: start, clarify, and export with multiple templates. It appears functionally complete for its domain, though additional utilities (e.g., listing previous refinements) could be imagined.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources