ai.page

Take the next task from the commons

next_task

The commons' common task list, one task at a time: write what a concept is missing, translate it, check a version blind, revise one with problems, or fix a question learners nearly always miss. Use it when the person wants to contribute to ai.page. Returns the best task for the signed-in person, held for them for 30 minutes, with what is needed to do it and how to submit it.

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": "next_task"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	Take this task from list_tasks instead of the best one
`types`	No	Only these kinds of task

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations mark it non-read-only and non-idempotent, and the description supplies the reason: the task is selected for the signed-in person and 'held for them for 30 minutes', which explains both the state change and why repeat calls differ. It still omits what happens on expiry, whether the hold can be released, and failure behavior when no task is available.

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?

Two sentences, front-loaded with the resource and the task menu, then usage and return behavior. Dense but every clause carries information; the long run-on list of task verbs is the only slightly bulky part.

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?

No output schema exists, and the description covers the return: the best task for the signed-in person, the 30-minute hold, plus what is needed to do it and how to submit. What is missing is edge behavior — empty commons, hold expiry, or whether re-calling replaces the held task.

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 coverage is 100%, so 'id' and 'types' are already documented. The description only loosely echoes five of the ten enum values ('write what a concept is missing, translate it, check a version blind...'), and never mentions roadmap, map, request, edge, or draw, so it adds little beyond the schema.

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

Purpose5/5

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

States a specific verb+resource ('take the next task from the commons') and enumerates the concrete task shapes (write, translate, blind check, revise, fix). An agent can distinguish it from list_tasks and the take_check/take_revision siblings without opening the schema.

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?

'Use it when the person wants to contribute to ai.page' gives a clear trigger condition. However, it never states when not to use it nor names alternatives (list_tasks, take_check, take_revision) in the description — the only routing hint lives in the schema's 'id' text.

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

All ai.page tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?