add_taskCapture commitments from conversations by adding tasks with optional due dates to StickyInc's floating pane.
Add a todo to StickyInc. The user sees it appear in their floating pane.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The task text, e.g. 'Call the dentist' | |
| due_at | No | Optional ISO 8601 datetime when this is due, e.g. '2026-04-24T15:00:00Z' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description includes the effect of immediate UI appearance, but lacks details on side effects, limits, or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences with front-loaded purpose and behavioral context, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple 2-param tool with no output schema; covers purpose and key effect, though missing error or limit info.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage with descriptions for both parameters; description adds no extra meaning beyond schema examples.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Add', resource 'todo to StickyInc', and user-facing effect 'appears in floating pane'. Distinct from sibling add_task_natural.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use vs alternatives like add_task_natural or when prerequisites apply.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Astralchemist/stickyinc'
If you have feedback or need assistance with the MCP directory API, please join our Discord server