agentic-task-system
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATS_ADAPTER | No | npm package name of the ATS storage adapter to load. Defaults to the TickTick adapter. | @reneza/ats-adapter-ticktick |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| findA | Read-only. Search the task store by free-text QUERY using available adapter signals plus Core keyword retrieval, fused via Reciprocal Rank Fusion. Adapters with embeddings add dense+sparse hybrid retrieval. Returns best-matching items with provenance. Use this for "what do I have about X". To find items like a KNOWN item instead, use |
| get_taskA | Read-only. Fetch one item (task/note) by its project id + task id, including the full markdown body, tags, and due date. Use after |
| list_projectsA | Read-only. List the projects / folders in the store, each with its id and name. Call this first to discover the projectId you need for |
| create_taskA | WRITE. Creates a new item (task/note) in the store — the agent→human write side of the two-way bus. Use to hand the human a note, action, or reminder. Side effect: a new item appears in their task app immediately. Returns the created item including its new id. To change an existing item instead, use |
| update_taskA | WRITE. Patches an existing item (partial update) — only the fields you provide change; omitted fields are left untouched. Side effect: the item is modified in the human's task app. Requires the item's projectId + taskId (get them from |
| undo_writeA | WRITE. Reverses a recorded write using the before-image the ledger captured: restores an updated task to its prior state, or deletes a task that was created. Omit actionId to undo the most recent undoable write. Pass dryRun to preview the plan without changing anything. Records a compensating |
| set_task_intentB | WRITE. Adds or updates portable execution intent inside the task body: desired outcome, why it matters, completion conditions, authority, constraints, and approval requirement. Preserves the human-authored body and works through every ATS adapter. |
| set_task_lifecycleB | WRITE. Sets portable lifecycle state and validity windows. Archived, expired, future, and superseded tasks are excluded by context assembly. |
| promote_explorationB | WRITE. Creates a committed execution item from exploratory material. The source body is not copied; the new item receives explicit outcome/completion metadata and an evidence link back to the source. |
| get_task_hierarchyA | Read-only. Returns the item role and its explicit parent relationship. Roles are exploration, goal, project, task, or unspecified. |
| set_task_hierarchyB | WRITE. Assigns an exploration/goal/project/task role and optionally replaces or clears the single explicit parent relationship. |
| evaluate_task_hierarchyA | Read-only. Deterministically checks whether a task still supports its parent objective and reports invalid role ordering, missing intent, cycles, invalid lifecycle state, and active explicit conflicts. |
| get_task_securityA | Read-only. Returns the portable trust, action, resource, denial, approval, and approver policy for one task. Unconfigured tasks default to untrusted content and no granted access. |
| set_task_securityB | WRITE. Sets a portable task security policy. This policy is a decision point for cooperating clients; it does not sandbox unrelated external tools. |
| check_task_accessA | WRITE/AUDIT. Evaluates one task-scoped access request and appends an allow or deny record. Requires an action, resource, and reason. Denial wins over allowance; untrusted high-risk actions and configured boundaries require approval. Fails closed if auditing fails. |
| add_task_linkB | WRITE. Adds a typed relationship from one task to another. Types express dependencies, evidence, decisions, outputs, supersession, support, or a general relation. Set allowMissing to record a forward link to a task that does not exist yet — it auto-resolves once the target is created (or run |
| resolve_task_linksA | Read-mostly. Back-resolves a task's forward links: for each stored link whose target now exists, refreshes the placeholder title to the real one. Returns which links resolved and which are still missing. Writes only if a title changed. |
| remove_task_linkA | WRITE. Removes one exact typed relationship from a source task. Returns removed=false when the relationship was already absent. |
| relate_taskA | WRITE. Auto-routes a relevant target into the right section by what it is: an active task goes to "## Related" (a typed link), a note goes to "## References", and a completed task is refused. Prefer this when you just know a target is relevant and do not want to choose the section yourself. Returns routedTo: "related" | "references". |
| add_task_referenceA | WRITE. Adds a resource the task consults (an external URL or a reference note) to its "## References" section. Use this for links and supporting notes; use add_task_link for relationships to other active tasks. Re-adding the same url updates its title/desc. |
| remove_task_referenceA | WRITE. Removes a reference (by url) from a task's "## References" section. Returns removed=false when the url was already absent. |
| list_task_referencesB | Read-only. Lists the resources (external URLs and reference notes) in a task's "## References" section. |
| task_graphA | Read-only. Traverses typed incoming and outgoing task relationships around one task. Returns nodes, edges, lifecycle validity, and unresolved references. |
| context_for_taskA | Read-only. Builds execution context for a task. Typed relationships come first, retrieval adds candidates, invalid lifecycle items are excluded, and every included item carries provenance. |
| record_actionA | WRITE. Appends an auditable agent action or outcome to the local ATS JSONL ledger, including sources, approvals, output, and whether the task advanced. |
| list_actionsA | Read-only. Lists action-ledger records, optionally filtered by task, agent, action, or advancement. |
| snapshot_task_eventsA | WRITE/LOCAL. Creates or replaces the local corpus-diff event checkpoint. This only observes task state; it never launches an agent or performs an external action. |
| poll_task_eventsA | WRITE/LOCAL. Diffs the current task corpus, durably stages deterministic event envelopes, then advances the checkpoint. Returns newly observed events plus the unacknowledged pending spool. Events are observation-only and must be acted on separately under normal ATS intent and security checks. |
| list_pending_task_eventsA | Read-only. Lists durable task-event envelopes that have not been acknowledged by a consumer. Task bodies are not stored in the spool. |
| acknowledge_task_eventsA | WRITE/LOCAL. Explicitly acknowledges one or more durable task-event ids and removes them from the pending spool. Unknown ids are reported without failing known acknowledgements. |
| similarA | Read-only. Find items semantically similar to a KNOWN item, given its id (not a text query — for text search use |
| url_forA | Read-only. Build a paste-ready deep link (a URL string) to an item in its native app, so you can hand the human a clickable reference. Does not open anything or write — pure id→URL construction. Returns the URL as a string. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/renezander030/agentic-task-system'
If you have feedback or need assistance with the MCP directory API, please join our Discord server