Skip to main content
Glama
Sign In
Specif-ai MCP Server

Specif-ai MCP Server

by doso
OverviewSchemaRelated ServersDiscussionsAdmin
TypeScript

get-user-stories

Retrieve user stories for a specific Product Requirements Document (PRD) by providing the PRD ID and current working directory, enabling efficient project specification management.

Instructions

Get User Stories for a particular PRD

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prdId": "<prdId>",
      "cwd": "<cwd>"
    },
    "name": "get-user-stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdYesAbsolute path where the tool is called from to auto-infer the project path. This path will be current working directory (cwd) from where the tool is called.
prdIdYesThe ID of the PRD to get user stories for

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?

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't specify whether this is a read-only operation, what format the user stories are returned in, potential errors (e.g., invalid PRD ID), or any rate limits. The description merely restates the tool's purpose without adding operational context.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, achieving optimal conciseness.

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?

Given the tool has no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'User Stories' entail (e.g., structured data, text descriptions), how results are returned, or error conditions. For a tool that likely returns complex data, more context is needed to guide the agent effectively.

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%, with both parameters well-documented in the schema itself. The description adds no additional parameter semantics beyond implying 'prdId' identifies the PRD, which is already clear from the schema. This meets the baseline score of 3 since the schema handles parameter documentation adequately.

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 clearly states the verb 'Get' and resource 'User Stories' with scope 'for a particular PRD', making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get-brds' or 'get-nfrs' which likely retrieve other document types, missing an opportunity to clarify its specific domain.

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 doesn't mention prerequisites (e.g., needing a valid PRD ID), exclusions, or relationships to sibling tools like 'get-prds' (which might list PRDs before selecting one). This leaves the agent without context for proper tool selection.

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

Related Tools