Exarp

Overview Schema Source Related Servers Discussions Admin

task_discovery

Discovers tasks from code comments, markdown task lists, and orphaned dependencies. Combines all sources for unified task management.

Instructions

[HINT: Task discovery. action=comments|markdown|orphans|all. Find tasks from various sources.]

Discovers tasks from:

action="comments": TODO/FIXME in code files
action="markdown": Task lists in *.md files
action="orphans": Orphaned Todo2 tasks (no dependencies)
action="all": All sources combined

📊 Output: Discovered tasks with locations 🔧 Side Effects: Can create Todo2 tasks (create_tasks=true)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "task_discovery"
  }
}

Input Schema

Name	Required	Default
`action`	No	all
`file_patterns`	No
`include_fixme`	No
`doc_path`	No
`output_path`	No
`create_tasks`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the side effect of potentially creating Todo2 tasks via create_tasks. However, it does not mention other behavioral traits like permissions, rate limits, or whether it modifies files (beyond creating tasks).

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 reasonably concise, using bullet points and emojis for clarity. It front-loads the main purpose and actions. Minor clutter from the hint line and emojis, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema (not shown) and 6 params. The description covers only one action parameter. While output schema may document return values, the lack of parameter descriptions and limited behavioral context (e.g., no mention of file_patterns filtering) makes it incomplete for proper tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fill the gap. It only explains the 'action' parameter and its values. The other 5 parameters (file_patterns, include_fixme, doc_path, output_path, create_tasks) are not described, leaving the agent without guidance on their meaning or usage.

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 clearly states the tool discovers tasks from various sources (comments, markdown, orphans, all). It explains each action, making the purpose specific. However, it does not explicitly distinguish from sibling tools like task_analysis or task_workflow, though the actions imply a unique discovery function.

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

Usage Guidelines3/5

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

The description lists the actions and their sources, giving implied usage context. It does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The hint at the start is somewhat generic.

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