@vibemap.ai/mcp-server

vibemap_list_user_stories

Read-only

Retrieve user stories for a project or feature, filtered by status or priority, with paginated results and full story details.

Instructions

List user stories for a project or feature. Filter by status, priority. Returns paginated results with full story detail.

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

Input Schema

Name	Required	Description
`limit`	No
`offset`	No
`search`	No
`status`	No
`priority`	No
`featureId`	No	Filter by specific feature
`projectId`	No	Filter by project (use featureId for more specific results)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.2Jul 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that results are paginated and contain full story detail, providing useful behavioral context beyond 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?

Two sentences, to the point. Could be more structured but no verbosity.

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

Completeness4/5

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

Given 7 parameters and no output schema, the description covers the key behaviors (paginated, full detail, filtering) but omits sorting order or maximum limit. Adequately complete for a list tool.

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 low (29%). The description mentions filtering by status and priority, adding meaning for those two enums, but does not explain limit, offset, or search parameters. Partial compensation.

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?

The description clearly states the tool lists user stories for a project or feature, with filtering and pagination. It distinguishes from siblings like create/update by focusing on reading.

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

Usage Guidelines3/5

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

The description implies use for listing user stories but does not explicitly state when to use this tool vs alternatives (e.g., using vibemap_list_features first). No when-not-to-use guidance.

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

Deploy Server