Alcoven

Gather what a task stands on

task_context

Read-only

A briefing on one task, or its background before work on it starts: gathers the task itself, what it links to, its notes, who worked on it, the documents most connected to it, and what changed in them since the person last looked.

Input Schema

Name	Required	Description
`task`	Yes	The task's § address.
`detail`	No	short, the default: the task, what it links to, the agreed documents that bind it and what changed in its folders, whole; then its notes, the most connected documents and who worked on them, the whole answer within 16,000 characters, where what does not fit is given as a § address with one line or counted in the last line. full: all of it, with no budget.
`project`	No	The project's slug, from open_project, like acme. Not needed when a § address names the project, or when the person is on one project.

Output Schema

Name	Required	Description	Default
`task`	Yes
`text`	Yes
`notes`	Yes
`agreed`	No
`linked`	Yes
`people`	Yes
`changes`	Yes
`expects`	No
`related`	Yes
`left_out`	No
`shortened`	No
`left_out_line`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "short, the default: the task, what it links to, the agreed documents that bind it and what changed in its folders, whole; then its notes, the most connected documents and who worked on them, the whole answer within 16,000 characters, where what does not fit is given as a § address with one line or counted in the last line. full: all of it, with no budget.",
+  "enum": [
+    "short",
+    "full"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / agreed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / left_out
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / left_out_line
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / shortened
```
Added value: +{
+  "type": "number"
+}
```

Changed1 schema field changedOct 24, 2026

addedOutput schema / properties / expects

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint true, openWorldHint false, and destructiveHint false, so the safety profile is covered. The description adds meaningful behavioral context by saying it gathers six related data classes and reports what changed relative to the person's last view; it stops short of permissions, rate limits, or pagination details, which are less critical here.

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 one front-loaded sentence that states the purpose before listing the gathered components. The list is dense but every item is relevant, with no filler or repetition.

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?

For a low-complexity, three-parameter read-only tool with full schema descriptions and an output schema, the description explains what is gathered and the temporal angle of the briefing. It lacks explicit sibling routing, but an agent has enough information to call it 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?

Schema description coverage is 100%, and the schema's detail enum description already explains the short/full budget behavior and the project parameter. The description only says 'one task' and does not add parameter meaning beyond what the schema provides, so baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb and resource: it 'gathers' a briefing on one task, including links, notes, people, connected documents, and changes. The composite scope distinguishes it in practice from single-purpose siblings like task, read, or what_changed, though it does not name any sibling explicitly.

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 phrase 'or its background before work on it starts' gives a clear usage context for when to call the tool. It does not name alternatives such as task, read, history, or what_changed, nor does it state exclusions, so it is clear context without routing guidance.

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

All Alcoven tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?