Skip to main content
Glama
Sign In
Waymark

Waymark

by SerjMihashin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_list

Read-only

List tasks filtered by status, project, assignee, or blocker. Query tasks with specific criteria for efficient task management.

Instructions

List tasks by status, project, assignee, or blocker.

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
statusNo
blockedNo
created_byNo
project_idNo
assigned_toNo
claimed_by_agentNo
created_by_agentNo
assigned_agent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations provide readOnlyHint=true, but description adds no behavioral context (e.g., pagination, ordering, response format). Does not contradict annotations.

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?

Single sentence of 8 words, highly concise. Front-loaded with filtering capabilities but could benefit from structuring or additional context.

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

Completeness2/5

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

Complexity is moderate with 9 optional parameters and no output schema. Description fails to mention response format, ordering, pagination, or the default behavior when no filters applied.

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 0% so description must compensate. It explains four parameters (status, project, assignee, blocker) but omits limit, created_by, and agent-related fields. Partial compensation for low coverage.

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?

Description clearly states verb (List) and resource (tasks) and mentions filtering dimensions (status, project, assignee, blocker). Differentiates from sibling tools focusing on memory or mutation.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like memory_search or task_search. Does not mention it is read-only or that it returns unfiltered tasks if no parameters provided.

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