Skip to main content
Glama

Prompts

prompts

Draft or improve coloring-page and cover prompts (batch, inspire, improve, covers, analyze, sync). One batch is 1–50 coloring pages; covers are separate calls. Does not spend image tokens.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare the operation non-read-only, non-destructive, and closed-world, so the description's cost note ('does not spend image tokens') and the 1-50 batch bound add real context. It never says whether prompts are persisted, what 'sync' or 'analyze' write, or what any call returns, which matters for a flagged non-read-only tool.

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?

Three short sentences, front-loaded with the purpose before the constraints. The op list in parentheses is dense but informative; little is wasted.

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

Completeness3/5

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

For a tool whose schema is a large oneOf across seven operations with no output schema, the description should convey what each op produces or requires. It covers scope and the batch limit but leaves per-op behavior entirely to inference.

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?

Reported schema description coverage is 100%, giving baseline 3. The description contributes only the batch size bound (1-50) and the cover/batch split; it does not explain the discriminator ops or op-specific requirements like currentPrompt for improve or applied for sync.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Draft or improve coloring-page and cover prompts') and enumerates the op values (batch, inspire, improve, covers, analyze, sync). It distinguishes itself from sibling 'generate' by noting it does not spend image tokens. However, the ops are only named, not explained, so an agent cannot tell what 'sync' or 'analyze' actually accomplish.

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

Usage Guidelines3/5

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

'Does not spend image tokens' implies this is the cheap drafting step before generation, and 'covers are separate calls' implicitly separates batch from cover usage. But no explicit when-to-use vs. when-to-use-generate statement or prerequisite ordering is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources