Skip to main content
Glama

problem_decomposition

Break down complex problems into manageable sub-problems and tasks. Organize hierarchical tasks with dependencies, resources, and risks for systematic problem-solving.

Instructions

Breaking down complex problems into manageable sub-problems and tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoThe scope and boundaries of this problem decomposition.
metricsNoMetrics and analysis of the decomposition.
problemYesA clear and comprehensive description of the problem to be decomposed.
versionNoVersion of this decomposition.
createdByNoWho created this decomposition.
objectivesNoThe main objectives to be achieved through this decomposition.
createdDateNoWhen this decomposition was created.
methodologyNoThe methodology or approach used for decomposition (e.g., 'Work Breakdown Structure', 'Feature-driven').
reviewNotesNoNotes from reviews of this decomposition.
lastModifiedNoWhen this decomposition was last modified.
decompositionYesA hierarchical list of tasks that the problem is decomposed into.
decompositionIdYesA unique identifier for this decomposition session.
completenessCheckNoChecklist items to verify completeness of the decomposition.
alternativeApproachesNoAlternative ways the problem could have been decomposed.
Behavior2/5

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

No annotations are present, and the description fails to disclose behavioral traits such as side effects, persistence, or prerequisites. The agent is left unaware of important details like whether this tool creates, reads, or modifies data.

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

Conciseness2/5

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

The description is extremely concise (one sentence), but it lacks necessary detail for a complex tool with 14 parameters and nested objects. It is under-specified rather than efficiently concise.

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

Completeness2/5

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

Given the tool's complexity (14 parameters, nested objects, no output schema) and many sibling tools, the description is grossly inadequate. It does not explain the decomposition structure, task hierarchy, or how to interpret the input, leading to high risk of misuse.

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 100%, with all 14 parameters having descriptions. The tool description adds no parameter-specific information beyond what the schema already provides, so the baseline score of 3 applies.

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

Purpose3/5

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

The description states a clear purpose: breaking down complex problems into sub-problems and tasks. However, it is generic and does not differentiate from sibling tools like 'recursive_thinking' or 'structured_argumentation', which also involve decomposition. The verb phrase is present but lacks specificity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With many sibling tools focused on reasoning and problem-solving, the description offers no context about appropriate scenarios or when to avoid this tool.

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/emmahyde/thinking-patterns'

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