@createworker/mcp

Official

Overview Schema Source Related Servers Discussions Admin

Get knowledge doc

knowledge_get

Retrieve a knowledge document by its unique ID. Access stored information needed for your AI-driven tasks and workflows.

Instructions

Get a knowledge document by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "docId": "<docId>"
    },
    "name": "knowledge_get"
  }
}

Input Schema

Name	Required	Description	Default
`docId`	Yes	the document id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

A3.5/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 the full burden for behavioral disclosure. It does not mention authentication, error handling (e.g., if doc doesn't exist), or any side effects. The description is tautological beyond the action.

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?

Single sentence of 6 words, front-loaded, no wasted words. Highly concise and directly gives the purpose.

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?

The description is adequate for a simple get operation, but lacks details on return format or expected output. Since no output schema is provided, this gap reduces completeness.

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 schema description covers docId as 'the document id' with 100% coverage. The description adds 'by id' but does not provide additional meaning beyond the schema. Baseline 3 applies.

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 'Get', the resource 'knowledge document', and the method 'by id'. It distinguishes from sibling tools like knowledge_list (list) and knowledge_create (create).

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 does not explicitly state when to use this tool versus alternatives. The context of retrieving a specific document by ID is implied, but no when-not-to-use or alternative tool mentions are provided.

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