Skip to main content
Glama

knowledge_write

Upsert an entity knowledge page by slug with title, domain, markdown body, and supporting citations. Pages with only conversation citations are stored as provisional until sourced externally.

Instructions

Upsert an entity page by slug. On an existing slug: body REPLACES by default (mode: "append" adds to it instead), title/domain follow the write, and citations are always appended with exact-duplicate dedup — safe to re-send. Knowledge is true independent of Jonathan — if it is about Jonathan or our work, store it in memory instead. Epistemic gate (§E1): a page whose ONLY citation support is source_kind="conversation" is stored provisional, not sourced. Requires at least one citation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesSynthesized markdown body for the entity page (max 64 KB)
modeNoBody combine mode when the slug already exists: "replace" (default) overwrites the stored body; "append" adds this body after the existing one. Citations are appended (deduped) in both modes. Ignored when creating a new page.
slugNoEntity key for upsert — stable URL-safe identifier. Derived from title if omitted.
titleYesPage title — the entity name (e.g. "Mutable Instruments Rings")
domainYesDomain tag, e.g. "music/eurorack", "programming/typescript". Hierarchical string; sub-domains queryable via prefix filter.
citationsYesSupport citations. At least one required. All-conversation support → page stored provisional.
freshness_anchorNoThe version/date the page's claims are valid as-of — e.g. "Syntakt OS 1.21" for a device, or "as of 2026-05" for a topic. Drives the verification engine: a page is re-verified when this anchor moves or the freshness SLA elapses.
Behavior4/5

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

Discloses body replace vs append, citation dedup, provisional storage for conversation-only citations, and requirement for at least one citation. No annotations provided, so description carries full burden. Does not mention rate limits or auth, but covers key behaviors.

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?

Four sentences, front-loaded with core purpose. Each sentence adds specific behavioral info. Could slightly condense, but efficient overall.

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?

Given 7 parameters and no output schema, description covers upsert mechanics, mode, slug, citations, and epistemic gate. Missing return value or error handling, but sufficient for an agent to use correctly.

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% with detailed descriptions. Description adds value by explaining mode default, slug derivation, domain hierarchical nature, and the effect of all-conversation citations on storage. Enhances beyond schema.

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?

Clear verb 'Upsert' and resource 'entity page by slug'. Distinguishes from siblings like knowledge_recall (retrieve) or knowledge_merge (merge). Specific about behavior on existing vs new slugs.

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?

Explicitly states when not to use: 'if it is about Jonathan or our work, store it in memory instead'. Describes epistemic gate for provisional storage. Could mention alternative tools, but the context is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jbarket/loom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server