Entalpa Requirements MCP

Requirements Show

requirements_show

Read-onlyIdempotent

Show requirements and generated interfaces in an interactive view where the user can browse them and select items to discuss. Narrow it with the filters of requirement_items_list or explicit requirement/interface UUIDs, and name what it shows in title. Call it when seeing or picking items helps the user, not after every data read. The user sees the items in the view, so the result only counts them: do not list them again in your reply. Items the user selects become the view's context. When the user refers to items they selected or are looking at, read that context before answering: some hosts attach it to the message, others offer a tool that reads an app's or widget's context. To read the items yourself, use requirement_items_list.

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": {
      "project_id": "<project_id>"
    },
    "name": "requirements_show"
  }
}

Input Schema

Name	Required	Description
`kind`	No	Combined requirement item kind. Supported values: requirement, interface_requirement.
`flags`	No	Keep only items carrying at least one of these flags.
`title`	No	Short heading for the view, a few words naming what it shows in the user's terms, e.g. "Checkout demo: payment failures".
`story_ids`	No	Story UUIDs.
`project_id`	Yes	Project UUID (database id).
`content_key`	No	Keep only items whose content has this key set (e.g. implementation_status).
`subsystem_ids`	No	Subsystem UUIDs.
`requirement_ids`	No	Select these requirement UUIDs. Must be nonempty. When either selection list is supplied, only explicitly selected items are returned; other filters still apply.
`stakeholder_ids`	No	Stakeholder UUIDs.
`content_contains`	No	With content_key, keep only items whose content[content_key] contains this substring (case-insensitive).
`interface_contract_ids`	No	Select these interface contract UUIDs. Must be nonempty. When either selection list is supplied, only explicitly selected items are returned; other filters still apply.

Output Schema

Name	Required	Description
`shown`	Yes	Items the view shows.
`requirements`	Yes	Normal requirements among them.
`interface_requirements`	Yes	Generated interface requirements among them.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses critical behavior: the user sees the items in the view, the result only counts them, and selected items become the view's context. It also explains how hosts may attach that context and tells the agent to read it before answering when the user refers to selected items.

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 front-loaded with the core action, then covers narrowing the view, when not to call it, and how selection context works. Every sentence serves a clear operational purpose, with no filler or redundant restatement.

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

Completeness5/5

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

Given an output schema exists, the description does not need to document return values. It still supplies the essential missing context: the result only counts items, the user sees the view, and selected items become context that must be read before responding to references about them.

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 input schema already documents all 11 parameters, including the selection-list semantics and the title example. The description reinforces the purpose of title and the selection filters but does not add meaning beyond what the schema provides.

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 states a specific verb and resource: it shows requirements and generated interfaces in an interactive view where the user can browse and select items. It clearly distinguishes the tool from requirement_items_list by framing this as a visual selection surface rather than a data-read operation.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: call it when seeing or picking items helps the user, not after every data read. It also names the alternative for reading items directly, requirement_items_list, and explains how to narrow the view using filters or explicit UUIDs.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?