Skip to main content
Glama
talonicdev

talonic-mcp

Official
by talonicdev
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

List Agent Tasks

talonic_list_agent_tasks
Read-only

List Agent-stage tasks visible to your workspace credential, filter by status or pipeline, and paginate to find available external-agent work to process.

Instructions

List Agent-stage tasks visible to this Talonic workspace credential.

USE WHEN: looking for external-agent work to process; begin with status 'available'. To take a batch of one pipeline (e.g. 'take 10 tasks of pipeline X'), list with pipeline_id and status 'available', then claim each with talonic_claim_agent_task; a task another agent took returns HTTP 409, so skip it and take the next. NOT FOR: reading the immutable task payload (use talonic_get_agent_task) or taking a lease (use talonic_claim_agent_task). ARGS: optional status, pipeline_id, limit, and cursor. RETURNS: metadata only plus pagination.next_cursor.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 50).
cursorNoOpaque cursor from pagination.next_cursor.
statusNoOptional task-status filter.
pipeline_idNoOptional pipeline (run) UUID: only that pipeline's tasks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.90
    • addedInput schema / properties / pipeline_id
      Added value: +{
+  "description": "Optional pipeline (run) UUID: only that pipeline's tasks.",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. Addedv0.1.75

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), but the description adds real behavioral context beyond them: a task already taken by another agent returns HTTP 409, metadata-only results are returned, and pagination.next_cursor drives continuation. That is substantive operational detail an agent needs.

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 with the core purpose and organized into labeled USE WHEN / NOT FOR / ARGS / RETURNS blocks. The pipeline batching example earns its space by showing a real invocation pattern. No filler.

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?

Though there is no output schema, the description compensates by stating RETURNS: metadata only plus pagination.next_cursor, which tells the agent exactly what to expect and how to paginate. Combined with the strong usage guidance, nothing needed to call this correctly is missing.

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 limit, cursor, status, and pipeline_id are fully documented in the schema itself, and the description only restates them as 'optional status, pipeline_id, limit, and cursor'. The suggested starting value 'available' adds minor guidance but no new semantic detail. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List Agent-stage tasks') with a clear scope qualifier ('visible to this Talonic workspace credential'). It is immediately distinguishable from sibling list tools like talonic_list_decision_tasks or talonic_list_specs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit USE WHEN and NOT FOR sections name both the conditions for use and the alternative tools (talonic_get_agent_task for payloads, talonic_claim_agent_task for leases). It even describes the concrete workflow (list then claim) and how to handle 409 conflicts.

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