knowl

Overview Schema Source Related Servers Discussions Admin

knowl_synthesize

Create or refresh a single evidence-backed project understanding for a specific scope you name explicitly, such as "retrieval ranking". Use it when you need a deterministic synthesis of that subject, not for general session summaries.

Instructions

Create or refresh one deterministic evidence-backed project understanding. Use only for a scope the user explicitly asked to have synthesised -- never as background tidy-up, and never to summarise a session. This never runs automatically on normal writes.

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": {
      "scope": "<scope>"
    },
    "name": "knowl_synthesize"
  }
}

Input Schema

Name	Required	Description	Default
`scope`	Yes	The subject to synthesise, named explicitly, e.g. "retrieval ranking". One scope per call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.23.0Sep 16, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations only carry openWorldHint:false, so the description carries the behavioural burden. It discloses determinism, evidence-backed nature, and the automatic-execution constraint, which adds value. However, it does not explain what 'refresh' entails (e.g., whether it overwrites existing understanding) or any side effects. This is moderate coverage.

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 sentences with zero filler. The purpose is front-loaded, followed by clear usage exclusions. Every clause earns its place.

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?

For a single-parameter tool with no output schema and minimal annotations, the description adequately covers when to use, what it does, and key behavioural constraints. It could mention expected output or result format, but that is not critical for a synthesis operation where the agent likely just calls it. Overall it is complete enough.

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 the single parameter fully (subject to synthesise, example, one scope per call). The tool description adds no extra meaning about the parameter beyond what the schema already provides, so the 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 states a specific action (create or refresh) on a specific resource (evidence-backed project understanding). It clearly distinguishes itself from siblings by explicitly ruling out background tidy-up and session summarisation, so an agent can tell it apart from other knowl tools.

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 explicit usage conditions: only for scopes the user explicitly asked to synthesise, never as background tidy-up, never to summarise a session, and never runs automatically on normal writes. This is direct and unambiguous, though it does not name specific alternative tools.

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