camelotwebtools-mcp

camelot_user_story_generator

Idempotent

Generate structured agile user stories with acceptance criteria and story points directly in your browser, enabling clear requirements for development teams.

Instructions

User Story Generator: Generate structured agile user stories with acceptance criteria and story points.. Local browser processing. Canonical URL: https://www.camelotwebtools.com/tools/user-story-generator

Input Schema

TableJSON Schema

Name	Required	Description	Default
`role`	No	Agile persona, stakeholder role, or position	Autonomous AI Coding Agent
`action`	No	Action or command to perform	execute Camelot tools via native JSON-RPC 2.0 MCP
`benefit`	No	Employee benefit or key advantage	provide finished, unwatermarked client documents directly to users
`acceptanceCriteria`	No	List of functional conditions required for acceptance

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Execution status of the tool (success or error)
`prefillUrl`	Yes	Direct deep-link URL to view, edit, and export in Camelot Web Tools
`canonicalUrl`	Yes	Canonical web URL for this tool on camelotwebtools.com
`documentTitle`	Yes	Title of the generated document, report, or calculation output
`documentMarkdown`	Yes	Complete structured output and body formatted in clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 16, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already assert idempotency and non-destructiveness; the description adds only 'Local browser processing,' which implies data stays in-browser. It doesn't disclose output format, whether results are deterministic across runs, or any caveats about how acceptance criteria are used, but it doesn't 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is stated in one sentence, but the double period after 'story points..' and the canonical URL are unnecessary noise. It is concise overall, though slightly unpolished.

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

Completeness3/5

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

With an output schema present, the description doesn't need to explain return values. However, it lacks context on how the tool consumes parameters, any limits on input length, or what 'local browser processing' means for a multi-turn agent workflow, making it adequate but not complete.

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 100%, and the description doesn't add parameter-level semantics beyond mentioning 'acceptance criteria.' The 'story points' phrase suggests output content, not parameter meaning, so the schema carries the descriptive burden.

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 'Generate structured agile user stories with acceptance criteria and story points' – a specific verb and resource. It is distinguishable from siblings by its focus on user stories, though it doesn't explicitly name alternatives. The redundant title and canonical URL add little but don't harm clarity.

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 other generators, no mention of prerequisites, audience, or alternative tools. 'Local browser processing' hints at a technical context but not when to select this over siblings like camelot_agile_roadmap_planner.

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

Deploy Server