flompt

decompose_prompt

Decompose a raw prompt into structured blocks (role, objective, context, constraints, etc.).

Uses AI (Claude/OpenAI) if an API key is configured on the server, otherwise
falls back to keyword-based heuristic analysis.
Returns a JSON list of blocks ready to edit or pass to compile_prompt.

Args:
    prompt: The raw prompt string to decompose.

Returns:
    A summary of extracted blocks + the full JSON to pass to compile_prompt.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prompt`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full transparency burden. It discloses the dual-mode operation (AI vs heuristic) and the return format (summary + JSON). It does not cover error cases or side effects, but for a decomposition tool, the behavior is well-communicated.

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 focused and well-structured with a short summary and explicit Args/Returns sections. It avoids fluff, though the returns section could be more precise about the output shape.

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 tool's simplicity (one parameter) and that an output schema exists, the description provides sufficient workflow context and behavioral notes. It could mention input size limits or API key requirements, but overall it is complete for the complexity.

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 description coverage is 0%, so the description must compensate. The Args section states 'prompt: The raw prompt string to decompose', adding minimal context beyond the parameter name. For a single self-explanatory parameter, this is acceptable but not rich.

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 states the specific action and resource: 'Decompose a raw prompt into structured blocks' with examples of block types. This clearly distinguishes it from siblings (compile_prompt assembles, list_block_types enumerates).

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?

It provides usage context by mentioning the tool's output is 'ready to edit or pass to compile_prompt', indicating a workflow. It also explains the fallback heuristic mode when no API key is configured. However, it does not explicitly state when to avoid this tool or compare with alternatives.

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

All flompt tools Inspect

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.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a unique role: decompose_prompt converts raw text to structured blocks, compile_prompt converts blocks to XML, and list_block_types provides reference metadata. No two tools serve the same function.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern with snake_case: compile_prompt, decompose_prompt, list_block_types. The verbs are distinct and descriptive.

Tool Count5/5

With three tools, the server covers the essential workflow of decomposition, compilation, and type reference without redundancy. This is an appropriately scoped toolkit for a focused purpose.

Completeness5/5

The toolkit provides the full pipeline from raw prompt to compiled XML, plus the necessary reference for known block types. There are no obvious missing operations for the intended workflow.

Resources

Need Help?