Skip to main content
Glama
Sign In
Cortex Intelligent

Cortex Intelligent

by adyoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

knowledge_list_documents

Retrieve stored knowledge documents newest first, with pagination controls to browse large collections. Use limit and offset to page through results.

Instructions

List stored knowledge documents (newest first, paginated)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax documents to return
offsetNoSkip this many documents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses ordering (newest first) and that results are paginated, but says nothing about auth requirements, return shape, or total counts, leaving meaningful behavioral gaps for a no-annotation tool.

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?

A single front-loaded sentence with zero filler; the core action leads and the qualifiers are compactly parenthesized. Every element earns its place.

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

Completeness4/5

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

For a simple two-optional-parameter list tool with no output schema and full schema coverage, the description covers purpose, ordering, and pagination adequately. It is nearly complete, with only the non-differentiation from retrieval/search siblings as a residual gap.

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 limit and offset are already documented in the schema. The description only echoes "paginated" without adding syntax, defaults, or boundary meaning beyond what the schema provides, matching the baseline 3.

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?

States a specific verb+resource ("List stored knowledge documents") and adds scope details (newest first, paginated). It does not explicitly distinguish itself from siblings like knowledge_search or knowledge_retrieve, which an agent could confuse it with, so it falls short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives. An agent must infer that this enumerates documents rather than fetching specific ones, but nothing in the text routes it against knowledge_search/knowledge_retrieve/knowledge_document_stats.

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