TaskMarket Data

Each tool targets a distinct resource: single task details, a list of tasks, and submissions for a specific task. There is no overlap in their purposes, and the descriptions make the boundaries clear.

The 'tm_' prefix is consistent, and both 'tm_get_task' and 'tm_list_tasks' follow a verb_noun pattern. 'tm_task_submissions' deviates slightly by omitting the verb, but it is still readable and unambiguous.

With only three tools, the surface is well-scoped for a read-only data provider focused on TaskMarket tasks. Each tool fills a necessary role without bloat or redundancy.

For a data server, the coverage is complete: you can list tasks, fetch full details of a single task, and retrieve submissions per task. There are no obvious missing operations for the stated purpose.