Skip to main content
Glama

task_list

Read-onlyIdempotent

Find tasks by title or ID and resolve ambiguous names before changing a task.

Instructions

Find tasks by title or ID. Resolve ambiguous names before changing a task.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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 safety is covered. The description adds the useful workflow hint that results are meant to disambiguate before a mutation, but says nothing about result ordering, pagination, or the default limit of 30.

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?

Two short sentences with no filler, and the core capability is front-loaded before the workflow advice. Nothing could be removed without losing information.

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?

An output schema exists, so return-shape explanation is unnecessary, and the read-only safety profile is annotated. The remaining gap is pagination/limit behavior for a list tool, which is a moderate omission rather than a blocking one.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It implies the query matches title or ID, which is genuinely additive, but the 'limit' parameter (default 30) is never mentioned and no match/substring semantics are given for query.

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 concrete verb and resource ('Find tasks') plus the lookup keys ('by title or ID'), so the agent knows the retrieval dimension. It does not distinguish itself from the sibling task_get, which likely also retrieves a single task, leaving the list-vs-fetch boundary implicit.

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?

'Resolve ambiguous names before changing a task' gives a real usage condition pointing forward to the update flow. However, it never states when to prefer task_get over task_list, nor what happens after ambiguity is found (does it return multiple matches?).

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