Entalpa Requirements MCP

Stories Create

stories_create

Create a story. With run_align_to_story, an alignment that fails leaves the story saved, and alignment_failure says why.

Input Schema

Name	Required	Description	Default
`story`	Yes	Story fields to create.
`project_id`	Yes	Project UUID (database id).

Output Schema

Name	Required	Description
`extra`	No	Optional free-form metadata object.
`content`	Yes	Story text.
`human_id`	Yes	Story human label (e.g. S-3), for creation and display.
`story_id`	Yes	Story UUID (database id).
`project_id`	Yes	Project UUID (database id).
`requirement_ids`	Yes	List of requirement UUIDs (database ids), not content.id.
`stakeholder_ids`	Yes	List of stakeholder UUIDs.
`lifecycle_rollup`	Yes	How the requirements underneath are distributed across lifecycle values.
`alignment_failure`	No	Present when `run_align_to_story` was asked for and the alignment did not finish: why. The story is saved all the same; retry with stories_update and `run_align_to_story: true`.
`outdated_requirement_ids`	No	Requirements written from an earlier text of this story, which may no longer match it. Re-propagating the story revisits them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / human_id

Added value: +{
+  "description": "Story human label (e.g. S-3), for creation and display.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "story_id",
-  "project_id",
-  "content",
-  "requirement_ids",
-  "stakeholder_ids",
-  "lifecycle_rollup"
-]New value: +[
+  "story_id",
+  "human_id",
+  "project_id",
+  "content",
+  "requirement_ids",
+  "stakeholder_ids",
+  "lifecycle_rollup"
+]

First observedOct 15, 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=false and destructiveHint=false. The description adds genuinely useful non-obvious behavior: a failing alignment leaves the story saved anyway, and alignment_failure reports the cause. This is real context beyond the structured fields, though permissions and idempotency are not addressed.

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?

Two tight sentences, zero filler, with the primary action front-loaded and the edge-case caveat immediately after. Every clause earns its place.

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?

An output schema exists, so return values need not be explained, and the description covers the key alignment-failure edge case. It omits prerequisites (project existence) and how the nested story payload relates to project_id, leaving minor gaps for a nested-object create.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining the failure semantics of run_align_to_story (story persists, alignment_failure explains why), adding meaning the schema line alone does not convey.

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?

States a specific verb and resource ('Create a story'), so the core action is unambiguous. It does not distinguish this tool from sibling creation paths such as projects_make_stories_from_description or open_questions_convert_to_story, so an agent gets no help choosing among them.

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 mention of run_align_to_story implies a usage condition (create then align in one step), but there is no explicit when-to-use versus alternatives guidance, no prerequisites, and no exclusions. Usage is only hinted at.

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

All Entalpa Requirements MCP tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?