Skip to main content
Glama

list_tasks

Read-only

Discover available non-private tasks and their arguments, optionally filtered by project or invocation name/alias, to identify which qkrun tasks you can run.

Instructions

Discover available non-private tasks and their arguments. Returns project, project_root and tasks for every project, or only the selected project. Filter by invocation name or alias.

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

NameRequiredDescriptionDefault
filterNo
projectNoRegistered project alias or path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds genuinely useful context: results exclude private tasks and are grouped by project with project, project_root, and tasks fields, optionally narrowed to one project. It stops short of describing ordering or pagination behavior, so it adds modest value beyond annotations rather than rich behavioral detail.

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?

Three short sentences with the core purpose front-loaded, followed by return shape and filtering. Tight overall, though the return-shape sentence and the filtering sentence could be merged without loss.

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?

With only two optional parameters, a read-only annotation, and no output schema, most of what an agent needs is present, but the description leaves return-value details (task entry structure, ordering, what an 'argument' looks like) largely implicit for a tool whose whole job is discovery.

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?

Schema coverage is 50%: the project param is documented in-schema, but filter is bare. The description compensates by explaining that filtering works by invocation name or alias, and that omitting project returns all projects. That meaningfully fills the schema gap.

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

Purpose4/5

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

States a specific verb and resource ('Discover available non-private tasks') plus the return payload (project, project_root, tasks). It does not name run_task explicitly, so differentiation from the sibling is only implied by the discovery-vs-execution framing.

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 is implied rather than stated: the tool is for finding tasks and their arguments, which naturally precedes run_task, but the description never says when to use this versus invoking a task directly or what happens if no filter matches. No exclusions or prerequisites are given.

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

Deploy Server

Other Tools