Skip to main content
Glama
Sign In
superpos-mcp

superpos-mcp

Official
by Superpos-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

superpos_list_knowledge

List knowledge entries from a hive, with optional filtering by key prefix to narrow results.

Instructions

List knowledge entries in the hive, optionally filtered by key prefix.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
hive_idNo
key_prefixNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It correctly identifies the operation as listing (read-only), but fails to mention pagination behavior, ordering, or what happens when no filter is applied. The limit parameter hints at pagination but is not explained.

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 a single sentence, front-loaded with the verb, and contains no filler. However, it may be too brief given the complexity of the tool's parameters.

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

Completeness2/5

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

Given the three parameters and no annotations, the description lacks important contextual details such as pagination behavior (limit), the scope of hive_id (default hive), and the ordering of results. The output schema exists but is not referenced.

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?

The description adds meaning for the 'key_prefix' parameter (optional filter), but does not explain 'hive_id' (which hive, default null meaning current hive?) or 'limit' (max page size?). With 0% schema description coverage, the description should compensate more comprehensively.

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 clearly states the tool lists knowledge entries in the hive and supports an optional key prefix filter. It distinguishes from siblings like 'superpos_search_knowledge' (full-text search) and 'superpos_get_knowledge' (single entry).

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 description implies usage for listing with optional prefix filtering, but does not explicitly state when to use this versus alternatives like search or get, nor does it mention any exclusions or prerequisites.

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

Deploy Server

Other Tools