agent-ops-mcp

List tasks

list_tasks

Retrieve team tasks by status or assignee to track progress and identify work items needing attention.

Instructions

List tasks from the team tracker, optionally filtered by status or assignee.

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

Input Schema

Name	Required	Description	Default
`status`	No
`assignee`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 23, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It names the operation and filters, but does not state whether results are paginated, ordered, or limited, what task fields are returned, or any scope/authorization context. For a tool with no output schema or annotations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that starts with the verb and resource, then adds the filter conditions. It contains no filler or redundant information, making it an efficient definition.

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

Completeness3/5

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

The tool is simple with two optional parameters and no nested objects, and the description covers the resource and filters. However, with no output schema and no annotations, it leaves the return shape, pagination and ordering behavior, and default result set unspecified — the main missing context an agent would need.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by explicitly explaining both parameters as optional filters ('status or assignee'). It adds the semantic role of each parameter and their optionality, which goes beyond the bare schema property definitions, though it lacks formatting examples beyond the enum values.

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 ('List') and resource ('tasks from the team tracker'), and identifies the optional filters by status or assignee. This makes the tool's purpose unmistakable and distinguishes it from siblings like get_task (single task retrieval) and create_task (creation).

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 clearly implies this tool is for retrieving a collection of tasks, with optional filtering, but it does not explicitly name alternatives or state when not to use it. There is no guidance about using get_task for a specific task or search_docs for document searches, so the routing is left to inference.

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

Deploy Server