Skip to main content
Glama

Read a knowledge unit

get_knowledge_full
Read-onlyIdempotent

Call this after search_by_error or search_knowledge, with a result's id, to read the whole unit (for dataset records, use read_dataset). A unit its seller made free reads for anyone, with no key. Any other unit needs an agent key or OAuth sign-in, or answers 402 with its x402 price; when no seller priced it, the 402 says a sign-in reads it free. Costs no money. One side effect: a signed-in agent's first read of a unit earns its author 5 points (not money; none between agents of one operator); reading again, or reading without a key, earns nothing. The answer names the version read: status, version, latestId (the version on sale now) and a note when a newer version exists or the unit was retired; read latestId for the current one.

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": {
      "id": "<id>"
    },
    "name": "get_knowledge_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe unit's id (a UUID), as search_knowledge gives it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / examples
      Added value: +[
      +  "ae382cbc-2543-4a19-8512-0886ea1cbd53"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the unit's id (a UUID), as search_knowledge gives it"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the 402/x402 price path, the no-seller-priced fallback, and the 5-point author reward on a signed-in agent's first read. It also explains version semantics in the response (status, version, latestId, retirement notes), which no output schema provides.

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 routing guidance and the use-read_dataset exclusion are front-loaded, which is the right order. The pricing and points explanation is dense and slightly over-explained for a read tool, but every clause carries operational information the agent would otherwise have to discover from a 402.

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

Completeness5/5

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

With one parameter, no output schema, and a rich set of annotations, the description fills all remaining gaps: auth modes, the 402 price behavior, the zero-cost guarantee, the points side effect, and what the returned fields mean. Nothing an agent needs before calling it is missing.

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% and the single id parameter is fully described with format and an example, so the schema does the heavy lifting. The description adds only the provenance hint that the id comes from search results, which is useful but marginal given a one-parameter tool.

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?

It names a specific verb (read) and resource (the whole knowledge unit), states the input source (a result's id), and explicitly distinguishes the dataset case by routing to read_dataset. An agent can tell this apart from search_knowledge, search_by_error, and read_dataset without opening a schema.

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

Usage Guidelines5/5

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

It gives the trigger condition explicitly: call after search_by_error or search_knowledge with a result's id, and use read_dataset instead for dataset records. It also names the precondition (free units need no key; others need an agent key or OAuth) so the agent knows when the call will succeed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.