Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

task_list

Read-only

List human tasks assigned to you or your tenant.

Returns tasks for people or agents: approvals, reviews, manual inputs and scheduled work. Tasks come from workflow approval steps and from task_create.

Filters:

  • status: Filter by task status (not_started, triaging, agent_working, ready_for_review, completed, cancelled, expired; "pending" means not_started)

  • priority: Filter by priority (low, medium, high, urgent)

  • limit/offset: Pagination (default limit: 20, max: 100)

Returns task details including title, description, status, priority, and due date.

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
limitNoMaximum number of tasks to return (default: 20, max: 100)
offsetNoNumber of tasks to skip (default: 0)
statusNoFilter by task status: not_started (pending), triaging (in_progress), agent_working, ready_for_review, completed, cancelled, expired
priorityNoFilter by priority: low, medium, high, urgent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: the tenant/user scoping of results, the origin of tasks, and pagination defaults (20) and ceiling (100), which are not all restated verbatim in the annotations.

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?

Front-loaded one-line summary, then a short explanatory sentence, then a bulleted filter block — the structure is scannable and every line carries either scope, origin, or parameter facts. No filler or hedging language.

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

Completeness5/5

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

With no output schema, the closing sentence about returned fields (title, description, status, priority, due date) is exactly what is needed to fill that gap. Combined with the scope, origin, and pagination details, an agent has everything required to call this correctly.

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 description coverage is 100%, so every parameter is already documented in the schema, including the status enum values and the 'pending' alias. The description's filter section largely mirrors those schema strings rather than adding new meaning, so baseline 3 applies.

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?

The opening sentence gives a specific verb and resource plus a scope qualifier ('assigned to you or your tenant'), and the follow-up enumerates what a task is (approvals, reviews, manual inputs, scheduled work). The verb 'list' inherently separates it from siblings task_create/task_update/task_complete, but none of those siblings are named so the differentiation is implicit rather than stated.

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?

The description explains where tasks originate ('workflow approval steps and from task_create'), which tells an agent when this tool is the right one to reach for. It stops short of explicit exclusions or of routing to task_complete/task_update once a task is found, so there is no full when-not guidance.

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

All Spaces by Peakflo toolsInspect
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.

Resources