Skip to main content
Glama
Sign In
linklore

linklore

Official
by linklore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

doc_rollup

Collects all lore linked to a document and generates an AI summary draft, turning scattered knowledge into a concise overview.

Instructions

[read-only] doc_rollup(id) — collects lore linked to a doc into an AI-summary draft.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doc_rollup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
helpNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description declares the tool as read-only, providing a key behavioral trait. However, it does not explain whether the summary draft is persisted, how AI is invoked, or any side effects, leaving ambiguity.

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?

The description is extremely concise: a single sentence with a function signature. Every part serves a purpose, and there is no redundant information.

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

Completeness2/5

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

Given two parameters and an output schema, the description omits explanation of the 'help' parameter and the nature of 'lore' or 'AI-summary draft'. It is incomplete for a tool with no annotations or further context.

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

Parameters2/5

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

Schema description coverage is 0%. The description only hints at 'id' in the signature but provides no explanation of its meaning or the 'help' parameter. The description adds minimal value beyond the 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?

The description uses a specific verb ('collects') and resource ('lore linked to a doc'), clearly stating the action and result ('AI-summary draft'). The '[read-only]' prefix distinguishes it from sibling tools that may modify data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusions.

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

Deploy Server

Other Tools