@createworker/mcp

Official

by CreateWorkerAI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

List knowledge docs

knowledge_list

Retrieve a paginated list of organization knowledge documents. Control results with cursor and limit parameters.

Instructions

List the org's knowledge documents (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"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only notes 'paginated' but omits details like default pagination behavior, order of results, or any side effects. This leaves significant gaps for an agent to infer correct invocation.

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, efficient sentence of 8 words that conveys the core action. However, the extreme brevity sacrifices important details, making it slightly too terse for optimal usefulness.

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 tool's simplicity and lack of output schema, the description provides minimal information. It lacks details on pagination mechanics, default behavior, and the nature of knowledge documents, leaving the agent with incomplete context for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% coverage (no descriptions for 'limit' or 'cursor'), and the description only adds 'paginated', which hints at their purpose but does not explain their semantics (e.g., cursor as opaque token, limit as max page size). The description compensates poorly for the missing schema documentation.

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 verb 'list' and the resource 'the org's knowledge documents', which uniquely identifies the tool's purpose among siblings. It distinguishes from related tools like knowledge_get (single document) and knowledge_create (creation) without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates this is for listing knowledge documents and mentions pagination, providing clear context. Although no explicit when-not-to-use or alternatives are given, no sibling tool duplicates this functionality, so the guidance is adequate for correct usage.

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