Skip to main content
Glama
simplepush

Simplepush MCP Server

Official
by simplepush
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

Append a subtask to an earlier task

append_subtask

Append follow-up questions or checklist items to an already sent push task. The token from send_task determines whether one task or every instance in a group gets it; answers are collected individually.

Instructions

Add a follow-up question or checklist item to a task sent with send_task. Pass the append_token from that result: a task's token appends to that one task; a group's token appends to every instance of the group (narrow with instances). Subtasks take the same content, inputs and reply as send_task and are answered on their own; read them with get_task (the chain) or get_group_status. Never waits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNoPublic https URLs attached as links.
replyNoOpen a comment thread on the subtask: `one-shot`, `sticky` or `one-time-per-user`.
titleNoShort heading. Always set one: the chain and the overviews identify subtasks by title, not content.
inputsNoThe inputs the recipient fills in, in display order.
contentNoBody of the subtask. Required unless `inputs` is given.
markdownNoRender `content` as Markdown.
instancesNoWith a group token: only these instance task ids get the subtask. Omit for every instance.
auto_commitNoDefault false: one Submit for all inputs. true: each input is submitted as filled.
append_tokenYesThe append_token returned by send_task (task or group).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses important behaviors: 'Never waits' indicates an asynchronous operation, and it explains group token behavior (appends to all instances unless narrowed with 'instances'). It also clarifies that subtasks are answered independently and how to retrieve them.

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 a single paragraph with about four sentences, conveying necessary context without excessive verbosity. It is well-structured, though longer than the ideal two-sentence example.

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?

The description covers key usage context: how to reference the original task, how to narrow instances, and how to retrieve subtask responses. It omits error conditions and return values, but these are not required for basic usage and the description is sufficiently complete for an agent to call the tool correctly.

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?

The schema provides 100% coverage with detailed descriptions for all parameters. The tool description adds general context about append_token and instances but does not offer additional semantic clarity beyond the schema's own descriptions for individual parameters.

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: adding a follow-up question or checklist item to a task created by send_task. It explicitly identifies the resource (tasks/groups) and the scope (single task or specific instances).

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 context by referencing send_task and explaining how to read subtask responses via get_task or get_group_status. It does not explicitly name alternative tools, but the relationship to send_task and retrieval is clear enough to infer appropriate usage.

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