Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_API_KEYNoGoogle API key for using Gemini as the judge
OPENAI_API_KEYNoOpenAI API key for using GPT as the judge
PROMPTEST_MODELNoForce a specific model name (e.g., claude-sonnet-4-20250514)
ANTHROPIC_API_KEYNoAnthropic API key for using Claude as the judge
OPENROUTER_API_KEYNoOpenRouter API key for using any model via OpenRouter
PROMPTEST_PROVIDERNoForce a specific provider: anthropic, openai, google, or openrouter

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
grade_promptA

Scores a prompt you're about to send (or just sent) to an AI coding assistant against Promptest's validated 5-category rubric (Specificity, Clarity, Scope, Verification, Constraint Calibration). Returns an overall grade, category breakdown, and CRG-RIS-backed guidance. Returns a taskId — call log_outcome with that taskId once you know how it actually went, to build a personal track record of what your prompting style actually predicts.

log_outcomeA

Records what actually happened after a prompt (previously scored via grade_prompt) was used — whether it succeeded, how many turns/messages it took to resolve, whether the fix stayed in scope, and whether the prompt named the bug's root cause and location. This is the data that lets Promptest MCP tell you what actually predicts good outcomes for YOUR prompting style, not just what the rubric guesses in the abstract.

get_prompting_historyA

Returns your personal history of graded prompts and logged outcomes, plus aggregate stats (average score, success rate, and — the key CRG-RIS finding — average turns-to-resolve when you named the root cause/fix location vs. when you didn't).

explain_rubricA

Explains Promptest's 5-category rubric and the CRG-RIS study findings behind this MCP's guidance, without grading anything. Useful for understanding what the scores mean before you start.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct and non-overlapping purpose: explaining the rubric, retrieving history, grading a prompt, and logging outcomes. No ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., explain_rubric, grade_prompt), making them predictable.

Tool Count5/5

Four tools is an appropriate and focused number for the domain of prompt assessment and tracking, covering the essential workflow without being too sparse or excessive.

Completeness5/5

The tool surface covers the complete cycle: learn the rubric, grade a prompt, log the outcome, and review personal history. No obvious gaps.

Maintenance

ActivityStale
ResponsivenessNo issues