Entalpa Requirements MCP

Packs Get

packs_get

Read-onlyIdempotent

Get a pack and every concern with its owners: one of the user's, one shared with them, or Entalpa's (read as published). A concern is a user story from the owner who has it. can_edit says whether packs_update may change it. Uses no AI and no credits.

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": {
      "pack_id": "<pack_id>"
    },
    "name": "packs_get"
  }
}

Input Schema

Name	Required	Description	Default
`pack_id`	Yes	A pack's UUID, from packs_list.

Output Schema

Name	Required	Description
`title`	Yes
`owners`	Yes
`pack_id`	Yes	A pack's UUID, from packs_list.
`problem`	No	Why it cannot be used yet, if it cannot.
`can_edit`	Yes	Whether packs_update may change it.
`concerns`	Yes
`by_entalpa`	Yes	Published by Entalpa for everyone, and read as published.
`description`	No	What the pack checks.
`version_name`	No	The published version read.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behavior, and the description adds genuinely new context: no AI usage, no credit cost, and that published packs are read as published. The can_edit explanation clarifies what the caller may do next, which annotations cannot express.

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?

Three compact sentences, front-loaded with the action and scope, with no filler. The middle sentence defining 'concern' is slightly awkward but earns its place by disambiguating a non-obvious term.

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?

With an output schema present, return values need no explanation, and the description still covers access scope, cost, and the meaning of the can_edit field. Nothing an agent needs to call this correctly is missing.

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 single pack_id parameter is fully documented in the schema, including its provenance from packs_list. The description adds no format or constraint detail beyond that, so the baseline 3 applies.

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 opens with a specific verb and resource ('Get a pack and every concern with its owners') and enumerates the three access scopes (own, shared, Entalpa-published). It is clearly a single-item fetch, distinguishable from packs_list, though the domain jargon ('concern', 'Entalpa's') assumes familiarity.

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?

It implies when this tool applies by describing which packs are retrievable and by pointing at packs_update via the can_edit flag, but it never explicitly contrasts with packs_list or states prerequisites. Usage is inferable rather than spelled out.

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?