Skip to main content
Glama

Entalpa Requirements MCP

Packs List

packs_list
Read-onlyIdempotent

List the packs the user can check a project with: Entalpa's published packs (by_entalpa), then the user's own and those shared with them. Each has its concern count, a few example concerns, and problem when it cannot be used yet. With project_id, it leaves that project out and says when it was last checked with each pack (last_review_at). packs_get reads every concern; pass a pack_id to projects_review_with_pack. Uses no AI and no credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "packs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject UUID (database id).

Output Schema

NameRequiredDescriptionDefault
packsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses result semantics such as Entalpa packs first, then user/shared packs, concern counts, example concerns, problem state, and last_review_at. It also states that the operation uses no AI and no credits, which is behavioral context not present in the annotations.

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?

The description is information-dense and front-loads the main purpose, ordering, and alternative tools. It is mostly efficient, though the final sentence packs several sibling references and output details into a compact block.

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 and only one optional parameter, the description provides enough context to call the tool correctly and interpret the results. It covers scope, optional project_id behavior, result fields, and relevant sibling alternatives.

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 already 100%, so the baseline is 3. The description still adds meaning beyond the schema by explaining that project_id causes the project to be left out and enables last_review_at per pack.

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: list packs the user can check a project with. It also distinguishes packs_get, which reads every concern, and projects_review_with_pack for reviewing, so an agent can separate this from siblings without opening schemas.

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 explains when to pass project_id and what changes as a result: the project is left out and last_review_at is shown. It also names the alternative path: pass a pack_id to projects_review_with_pack, and use packs_get to read every concern.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources