santismm-knowledge

Official

by santismm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get an Agentic AI Knowledge Unit

get_knowledge

Read-onlyIdempotent

Retrieve a full knowledge unit by slug, or a single-locale body when a locale is specified. Use it after search or list_knowledge returns a slug to read the complete entry.

Instructions

Get one knowledge unit by slug. Returns the full entry, or a single-locale body if locale is given. Use this once search or list_knowledge has given you a slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_knowledge"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Knowledge unit slug, e.g. 'harness-engineering'.
`locale`	No	Language of the returned body. Default: en.

Output Schema

Name	Required	Description
`id`	No
`body`	No
`name`	No
`slug`	Yes
`tags`	No
`domain`	Yes
`locale`	No
`status`	No
`aliases`	No
`api_url`	Yes
`locales`	No
`related`	Yes
`summary`	No
`updated`	Yes
`version`	Yes
`category`	Yes
`evidence`	Yes	Evidence-First provenance: weight claims by this.
`fallback`	No
`featured`	No
`patterns`	No
`knowledge`	No
`frameworks`	No
`references`	Yes
`how_to_cite`	No	The citation, already formed — use it verbatim.
`resource_uri`	No
`technologies`	No
`canonical_url`	Yes
`resolved_locale`	No
`requested_locale`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Nov 6, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "es",
-  "pt"
-]New value: +[
+  "en",
+  "es",
+  "pt",
+  "fr",
+  "de",
+  "ja",
+  "zh"
+]

addedOutput schema / properties / how_to_cite

Added value: +{
+  "description": "The citation, already formed — use it verbatim.",
+  "type": "string"
+}

Changed6 schema fields changedv0.4.1Sep 2, 2026

addedInput schema / properties / slug / maxLength
```
Added value: +128
```
addedInput schema / properties / slug / minLength
```
Added value: +1
```
changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / aliases

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / resource_uri
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / required

Added value: +[
+  "domain",
+  "slug",
+  "category",
+  "updated",
+  "version",
+  "evidence",
+  "canonical_url",
+  "api_url",
+  "references",
+  "related"
+]

First observedv0.2.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the response shape changes with locale (full entry vs single-locale body), which is useful, but it does not cover failure behavior for a missing slug or any limits.

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?

Two tight sentences, front-loaded with what the tool returns before the routing advice. No filler and no restatement of the title.

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?

Purpose, the when-to-use trigger, and the locale-conditional return are all present, and an output schema plus rich annotations cover the rest. The only real gap is that error behavior for an unknown slug is unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description goes slightly beyond it by explaining the observable consequence of `locale` — you get only a single-locale body instead of the full entry. It does not add anything on `slug` beyond the schema's example.

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 and resource ('Get one knowledge unit by slug') and names the identifier used for lookup, so it is distinguishable from the list_/search_ siblings. It does not explicitly differentiate itself from other singular getters like get_article or get_pattern, which keeps it 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 Guidelines4/5

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

Gives an explicit usage condition: 'Use this once search or list_knowledge has given you a slug,' naming the upstream alternatives. There is no when-not guidance (e.g. what to do if you have no slug), but the required context is clear.

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