knowl

Overview Schema Source Related Servers Discussions Admin

knowl_evidence_list

Read-only

List evidence linked to a knowledge item to verify support before relying on low-confidence, contested, or outdated claims.

Instructions

List the evidence linked to one knowledge item. Use before relying on an item that is low-confidence, contested, or old enough that its support matters more than its claim.

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": {
      "itemId": "<itemId>"
    },
    "name": "knowl_evidence_list"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	No	Do this as another repo in this workspace, named as the manifest names it. Use when you are finishing THAT repo's work from here: the call applies to its store exactly as if you had run it there, so you read that repo's history rather than this one's. This tool only reads; nothing about naming a repo here writes to it. Omit it -- the normal case -- and everything applies here.
`itemId`	Yes	Knowledge item ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.23.0Sep 16, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows it is a safe read operation. The description adds the strategic context but does not disclose other behavioral traits (e.g., output format, ordering, or whether it returns all evidence or a subset). Given the annotations cover the key safety aspect, a 3 is appropriate; the description adds marginal value beyond the purpose.

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, no fluff. The core function is stated first, followed by a concise use-case rationale. Every word earns its place, and the description is front-loaded with the action.

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 simple read-only tool with two parameters and no output schema, the description is sufficient. It tells the agent what it does and when to use it. The only missing element is a hint about the output shape, but with no output schema and a straightforward 'list' operation, that is not a critical gap.

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 description coverage is 100%: both 'repo' and 'itemId' have descriptive text. The 'repo' parameter description is unusually detailed, explaining the cross-repo semantics. The tool description does not add any parameter-level information, so it relies on the schema. Baseline 3 is correct.

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 ('List the evidence linked to one knowledge item') and clearly identifies the resource. It distinguishes itself from siblings like knowl_recent or knowl_query by focusing on evidence for a single item, and even provides a motivational context (low-confidence, contested, old items).

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?

The description gives explicit when-to-use guidance: 'Use before relying on an item that is low-confidence, contested, or old enough that its support matters more than its claim.' It does not mention alternatives or exclusions, but the scenario is clear enough for an agent to decide when to invoke this tool.

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