Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

tasks_list

Read-onlyIdempotent

Lists a project's tasks ordered by recency, optionally filtered by status; excludes plan steps by default, but loads a plan's steps via slug or one task by globally unique ID.

Instructions

List a project's tasks, optionally filtered by status, newest first. By default plan-step tasks are excluded; pass plan= to list that plan's steps instead. Pass id= to load a single task by its globally-unique id (a direct lookup that ignores project/status/plan and needs no session scope).

Input Schema

NameRequiredDescriptionDefault
idNoload exactly one task by its globally-unique id; when set, project/status/plan are ignored and the response's tasks array holds just that task
planNooptional plan slug: list that plan's step tasks instead of the default (non-plan) tasks
statusNooptional status filter
projectNoproject slug; defaults to the bound session's project
sessionNothe session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.4
    • addedInput schema / properties / session
      Added value: +{
+  "description": "the session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description still adds real behavioral context: the default plan-step exclusion, the newest-first ordering, and the notable fact that an id lookup ignores project/status/plan and needs no session scope — a non-obvious escape hatch an agent could not derive from 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?

Three tight sentences, zero filler, and the primary behavior (list tasks, filtered, newest first) is front-loaded before the two alternate modes. Every clause carries information an agent needs to choose the right mode.

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?

For a read-only list tool with no output schema and five zero-required parameters, the description covers the defaults, both alternate modes, the response shape for the id path, and the session/crediting implication. Nothing needed to invoke it correctly is absent.

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 description coverage is 100%, so the schema already documents all five parameters and a baseline of 3 would be defensible. The description adds genuine framing on top: the mode-selection semantics of plan= vs. default vs. id=, and that the id path bypasses session scoping and returns a single-element tasks array.

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 (list a project's tasks) plus the ordering (newest first) and two alternate modes (plan-step listing, single-task lookup by id). It is immediately clear what the tool returns. It does not, however, name or contrast itself with the adjacent siblings (tasks_ready, tasks_claim), so an agent must infer the boundary between browsing and claiming work.

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 gives explicit conditional guidance: default excludes plan-step tasks, use plan=<slug> to see a plan's steps instead, use id=<task id> for a direct single-task lookup. What is missing is the 'when not to use this' side — nothing says to prefer tasks_ready for actionable work or tasks_claim to take a task.

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