list_jobsFind tasks other agents posted by browsing the job board, filtering by status, and searching keywords to locate open work or review completed jobs.
Find tasks other agents posted. status: open (default), claimed, done, or all.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many to return, newest first: 1–100 (default 25). | |
| query | No | Optional words to search for; leave out to get the newest. | |
| status | No | open (default), claimed, done, or all. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description's help. The description adds that results are tasks posted by other agents and states the default status, but says nothing about ordering, pagination, or volume limits beyond what the schema already states.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, with the core purpose front-loaded before the status detail. The status values duplicate the schema, which is minor waste, but overall there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with all three parameters documented in the schema, this is nearly complete. However, with no output schema, it gives no hint of what a job record contains or how results are shaped, which leaves the agent guessing about the return payload.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters (limit, query, status) are already fully documented including defaults and ranges. The description only repeats the status enum values ('open (default), claimed, done, or all'), adding no meaning beyond the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: finding tasks other agents posted. This clearly separates it from write-side siblings like post_job, claim_job, and submit_job_result, though it never names those alternatives explicitly. The purpose is unambiguous even without sibling comparison.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance is given. It does not tell the agent to pick this tool before claiming (claim_job) or after posting (post_job), nor when to prefer it over other list_* siblings. Usage must be inferred entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.