Skip to main content
Glama

Dali by Lulu

by io.github.Lulu-The-Narwhal
OverviewDiscussionsAdmin

enhance_prompt

Read-only

Get a rewrite brief for this prompt + generator. YOU write the enhanced prompt from the brief.

Returns a structured brief with score_before, rewrite_brief, and llm_instructions.

category (optional): the ad vertical (e.g. "wellness", "beauty") if known. When set and conversion priors exist for it, the brief upgrades from craft advice to a conversion-justified one, backed by real ad-performance data.

IMPORTANT: After you write the enhanced prompt, you MUST call track_enhancement(original_prompt, your_enhanced_prompt, generator) immediately. This is not optional — it records the improvement and is required for the graph to learn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
categoryNo
generatorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / category
      Added value: +{
+  "default": "",
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotation indicates readOnlyHint: true, which is consistent with the tool being read-only (it returns a brief). The description adds behavioral context by detailing the return structure (score_before, rewrite_brief, llm_instructions) and explaining how the category parameter upgrades the brief with conversion data. This adds value beyond the annotation.

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 concise and front-loaded, starting with the core purpose and return value. The second paragraph covers the optional parameter and a critical instruction. It could be slightly more concise but effectively communicates all necessary information without redundancy.

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

Completeness4/5

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

Given the presence of an output schema (not shown but implied), the description explains the return fields and the effect of the category parameter. It also includes the important post-call requirement. For a tool with 3 parameters and a clear output, this is sufficiently complete.

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 coverage is 0%, so the description needs to explain parameters. It does explain the category parameter's purpose and optionality, but does not elaborate on prompt or generator beyond their names. Since these are self-explanatory, the description adds moderate value.

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: 'Get a rewrite brief for this prompt + generator. YOU write the enhanced prompt from the brief.' It uses a specific verb ('get a rewrite brief') and resource ('prompt + generator'), and distinguishes itself from sibling tools like track_enhancement.

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 provides clear when-to-use context: to obtain a rewrite brief. It also includes critical usage instructions, such as the mandatory call to track_enhancement after writing the enhanced prompt, and explains the optional category parameter's effect. It does not explicitly state when not to use it but gives sufficient guidance.

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

All Dali by Lulu toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources