Arbituro

List jobs

list_jobs

Read-onlyIdempotent

List this project's jobs in the order people set, one line each: key, title, type, status and its kind, owner, agent, start and due days, priority, parts finished, the job it is part of, how well it is written down (shaped n/3), the days since anything happened on it, and who it is waiting on and for what. Unfinished jobs unless status says otherwise, 50 at a time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "list_jobs"
  }
}

Input Schema

Name	Required	Description
`after`	No	The key the last page ended on, to read the page after it.
`limit`	No	How many jobs to return, up to 100. Defaults to 50.
`owner`	No	Only the jobs this person owns, by name. Pass "me" for the person you act for, or "none" for the jobs nobody owns.
`partOf`	No	Only the jobs that are part of this job, by its key, e.g. FLAIR-3.
`status`	No	A status's name, or one of: open (the default: every unfinished job), not-started, underway, finished, dropped, all.
`project`	Yes	The project's key, e.g. FLAIR.
`untouchedDays`	No	Only the jobs nothing has happened on for at least this many days.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior: stable ordering set by people, a one-line-per-job shape, an implicit unfinished-status default filter, and a 50-per-page paging cadence.

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 opening leads with verb, resource and ordering before the long field enumeration, so it is front-loaded. The field list is dense but each item is a distinct output column, though the run-on enumeration is heavier than it needs to be.

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?

With 7 parameters and no output schema, the description usefully compensates by naming the returned fields and the default filtering and paging behavior. Cursor mechanics are left entirely to the schema, which is acceptable since the 'after' parameter documents itself.

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 every parameter is already documented in the schema. The description only restates the status default ('unfinished unless status says otherwise') and the page size ('50 at a time'), adding no filtering semantics beyond what the schema provides.

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?

The description states a specific verb and resource scoped to a project ('List this project's jobs') and enumerates exactly what one line of output contains, which lets an agent distinguish it from single-record siblings like get_job or search 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 Guidelines3/5

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

Usage context is implied by stating that unfinished jobs are returned unless status says otherwise, and by the page-size default, but the description never names an alternative tool or says when to prefer get_job, search, or what_happened over this list.

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

All Arbituro 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.