Skip to main content
Glama
LumabyteCo

Clarifyprompt-MCP

save_outcome

Records user verdict on optimized prompt outputs to update learning loops with few-shot examples and persistent memory facts, improving future prompt optimizations.

Instructions

Tell ClarifyPrompt whether an optimization's output was accepted, edited, or rejected. Feeds two loops: (1) the session ring buffer so accepted prior outputs are injected as few-shot examples into future similar prompts, and (2) the persistent memory layer via reflection — on accept/edit, ClarifyPrompt extracts atomic facts from the interaction and stores them; on reject, recent reflection facts from this session are invalidated. Reflection uses the same LLM you've configured; expect a 1–3s latency on local models.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optimization_idYesThe `id` returned from optimize_prompt
session_idYesThe `sessionId` returned from optimize_prompt. Required so the outcome lands in the right session bucket.
verdictYesaccepted = user used the output as-is; edited = user kept it with edits; rejected = user threw it away
diffNoOptional: the user's edited version or a diff. Helps reflection extract better facts.
skip_reflectionNoSkip the LLM-based fact extraction pass (faster, no facts learned)
Behavior5/5

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

No annotations are provided, but the description fully discloses the behavior: feeding the session ring buffer, triggering reflection for fact extraction/invalidation, and the latency impact on local models. It covers all significant side effects.

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

Conciseness5/5

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

The description is concise yet comprehensive. It front-loads the core purpose, then efficiently explains the two feedback loops and the reflection latency. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all essential aspects: the tool's function, its integration into two loops, behavior on each verdict, and a performance caveat. No output schema exists, but the side effects are fully described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% description coverage, but the tool description adds operational context (e.g., how 'diff' helps reflection, the effect of 'skip_reflection') that provides additional meaning beyond the schema.

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 it records the verdict of an optimization output (accepted/edited/rejected) and explains its role in two feedback loops, distinguishing it from sibling tools that handle other aspects of the optimization process.

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

Usage Guidelines4/5

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

The description implies usage after obtaining an optimization output, but does not explicitly state when not to use it or list alternatives. It provides clear context for when it is appropriate.

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

Install Server

Other Tools

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/LumabyteCo/clarifyprompt-mcp'

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