lore-mcp

kb_get_batch

Fetch full content for multiple KB entries by ID. Use after kb_search to retrieve content without multiple round trips.

Instructions

Fetch full content for multiple KB entries by ID. Use after kb_search to retrieve content without N+1 round trips.

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": {
      "kb_ids": "<kb_ids>"
    },
    "name": "kb_get_batch"
  }
}

Input Schema

Name	Required	Description	Default
`kb_ids`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Jun 4, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided; description only says 'Fetch full content' without stating whether it's read-only, safe, error behavior, or permission requirements. Limited behavioral insight.

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, front-loaded with action, then usage advice. No filler; every word earns its place.

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

Completeness3/5

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

Covers purpose and usage guidance adequately for a simple tool with output schema, but lacks behavioral and parameter details. Gaps in transparency and parameter semantics reduce completeness.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no parameter meaning or constraints beyond the schema (e.g., max 50 items not mentioned, no format guidance).

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?

Description clearly states the action ('Fetch full content') and resource ('multiple KB entries by ID'), distinguishing from sibling kb_search by advising use after search to avoid N+1 round trips.

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 recommends using after kb_search and explains benefit (avoid N+1). Does not mention when not to use or list alternatives beyond the sibling, but context is clear.

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