Clarifyprompt-MCP

list_packs

View all knowledge packs currently loaded in persistent memory. Filter by user or project scope to narrow results.

Instructions

List knowledge packs currently loaded in the persistent memory store.

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": "list_packs"
  }
}

Input Schema

Name	Required	Description	Default
`scope`	No	Filter by scope (e.g. 'user', 'project:myapp'). Omit to list all.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.8Jun 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the read operation ('list') but lacks details on permissions, rate limits, side effects, or result format.

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 a single sentence of 10 words, front-loaded with the action and resource, containing zero superfluous information.

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?

Given one optional parameter and no output schema, the description minimally covers the tool's purpose. However, it lacks usage guidance and behavioral details, leaving gaps for effective invocation among 22 siblings.

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% with a clear description of the 'scope' parameter including examples. The tool description adds the context 'currently loaded' but does not further enrich parameter semantics beyond the schema.

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 'List knowledge packs currently loaded in the persistent memory store,' with a specific verb and resource. It is distinct from siblings like load_knowledge_pack or unload_pack, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives such as memory_list_facts or list_categories. The description provides no context for selecting this tool over others.

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