Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
optimize_promptB

Analyze a raw prompt, detect ambiguities, compile an optimized version, score quality, and estimate cost across providers. Returns a PreviewPack for review.

refine_promptB

Refine a prompt by answering blocking questions or providing manual edits. Re-runs analysis and returns updated PreviewPack.

pre_flightB

Full pre-flight analysis: classify task, assess risk, route model, score quality. Returns complete decision bundle. Metered — counts as 1 optimization use.

check_promptA

Quick pass/fail check of a prompt. Returns score, top issues, and a suggestion. No compilation, no session.

approve_promptC

Approve the compiled prompt. Returns the final optimized prompt ready for use.

estimate_costB

Estimate token count and cost across providers for any prompt text. No session needed.

compress_contextB

Compress context (code, docs) by removing irrelevant sections. Returns pruned context with token savings.

classify_taskB

Classify a prompt by task type, reasoning complexity, risk level, and suggested profile. Free — no metering.

route_modelB

Route to the optimal model based on task complexity, risk, budget, and latency preferences. Returns recommendation with decision_path audit trail. Free — no metering.

prompt_statsB

Get aggregated optimization statistics: total count, average score, top task types, estimated savings.

prune_toolsA

Score and rank MCP tools by relevance to a task intent. Optionally prune low-relevance tools to save context tokens.

configure_optimizerB

Configure optimizer behavior: mode, threshold, strictness, default target, ephemeral mode, session limits. Supports config locking with passphrase protection.

get_usageB

Get current usage count, limits, remaining quota, and tier information.

set_licenseA

Activate a Pro or Power license key. Validates the Ed25519 signature offline and unlocks the corresponding tier.

license_statusA

Check current license status, tier, and expiry. Returns purchase link if no license is active.

save_custom_rulesA

Save custom governance rules to the local rules file (~/.prompt-control-plane/custom-rules.json). Validates all rules against the product schema, writes to disk, and returns the rule-set hash. Rules take effect on the next optimization. Works with any LLM connected to PCP. Enterprise tier only.

list_sessionsB

List all optimization sessions with metadata (no raw prompts). Free tool, not metered.

export_sessionA

Export full session details including raw prompt. Free tool, not metered.

delete_sessionA

Delete a single optimization session by ID. Returns deleted status. Free tool, not metered.

purge_sessionsB

Purge optimization sessions by age policy or delete all. Safe-by-default: requires explicit parameters. Free tool, not metered.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 20 tools

Disambiguation5/5

Each tool has a clear, distinct purpose covering different aspects of prompt optimization, session management, licensing, and configuration. No two tools appear to do the same thing; even similar-sounding tools like optimize_prompt and refine_prompt are clearly differentiated.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., approve_prompt, delete_session), but a few like license_status, prompt_stats, and pre_flight deviate with noun-noun or adjective-noun patterns, introducing inconsistency.

Tool Count4/5

20 tools is a reasonable number for a comprehensive prompt control plane. Each tool covers a distinct function, and the set feels scoped without unnecessary bloat or missing essentials.

Completeness4/5

The tool surface covers core workflows: optimization, evaluation, classification, compression, session management, licensing, and usage tracking. Minor gaps exist (e.g., no direct tool to retrieve compiled prompt without approval), but overall coverage is strong.

Maintenance

ActivityMaintained
ResponsivenessNo issues