VibeTape MCP Server

Overview Schema Source Related Servers Discussions Admin

list_tasks

Filter tasks by status, creator, assignee, and limit. Get targeted task lists for tracking development work and agent handoffs.

Instructions

List tasks with optional filters

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

Input Schema

Name	Required	Description
`limit`	No	Max results (default: 20)
`status`	No	Filter by status
`created_by`	No	Filter by creator
`assigned_to`	No	Filter by assigned actor

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 1, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states 'optional filters', which is already implied by the schema's optional parameters. It does not disclose return format, pagination, ordering, or access permissions.

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?

The description is a single concise sentence that efficiently conveys the core purpose without unnecessary verbosity. It is front-loaded with the action and resource.

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?

The tool has no output schema and no annotations, so the description should explain return values and any side effects. It does not, leaving the agent with limited information about the tool's behavior. However, the tool is relatively simple, so the gap is not as severe as with more complex tools.

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 the parameters are well-documented in the schema. The description's mention of 'optional filters' adds little beyond what the schema already conveys, so a baseline score of 3 is appropriate.

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 description 'List tasks with optional filters' clearly identifies the verb (list), resource (tasks), and mentions filtering capability. It distinguishes from sibling tools that operate on other resources like list_actors or list_moments, though it could be more specific about the scope of tasks.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or suggest other tools for different scenarios, leaving the agent to infer from the name alone.

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