Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

propose_task_split

Propose splitting an existing task into 2–10 smaller children. Writes a PENDING AISuggestion row that a human reviews + accepts in the normal Suggestions inbox. The agent should poll the suggestion id until status flips to ACCEPTED, then call add_subtasks to materialize the split. Use this when the brief reveals a task is too coarse to execute as one unit and you want explicit human approval before fragmenting the plan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "<taskId>",
      "children": "<children>",
      "rationale": "<rationale>"
    },
    "name": "propose_task_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesThe task you want to split. Must be visible to the caller.
childrenYes2–10 proposed child tasks. Each gets title + optional description / priority / estimatedHours.
rationaleYesWhy the agent thinks the parent should be split. Shown to the human reviewer. 1–2000 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the exact side effect (a PENDING AISuggestion row), where a human reviews it (Suggestions inbox), and the required agent behavior (poll the suggestion id until status flips to ACCEPTED). This is rich workflow context the annotations cannot convey.

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?

Four tightly packed sentences with the core action front-loaded, then side effect, then required follow-up, then the triggering condition. Every sentence carries distinct information and none is redundant.

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?

For a mutation tool with no output schema, the description supplies everything an agent needs: the artifact created, who reviews it, how to detect acceptance, and what to call next. Nothing critical is missing.

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 100%, so taskId, children, and rationale are already fully documented in the schema. The description restates the 2–10 child constraint and the 'existing/visible' task notion but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('propose splitting an existing task into 2–10 smaller children') and immediately clarifies the output artifact (a PENDING AISuggestion row). It also distinguishes itself from the sibling add_subtasks, which performs materialization rather than the proposal.

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

Usage Guidelines5/5

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

Explicitly states when to use it ('when the brief reveals a task is too coarse to execute as one unit and you want explicit human approval before fragmenting the plan') and names the follow-up tool (add_subtasks) needed to act on an accepted suggestion. Nothing is left implicit.

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

All Onplana toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources