Skip to main content
Glama
Sign In
knowl

knowl

by dat999zx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

knowl_recent

Read-only

Retrieve compact recent session context when lifecycle bootstrap is unavailable or an explicit refresh is needed. Returns active knowledge items and commits with configurable limits.

Instructions

Get compact recent session context only when lifecycle bootstrap is unavailable (including manual mode) or an explicit refresh is needed.

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": "knowl_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxCharsNoMaximum markdown characters; defaults to 3000.
itemLimitNoMaximum recent active knowledge items to return; defaults to 3.
commitLimitNoMaximum recent knowledge commits to return; defaults to 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.23.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is already established. The description adds that the return is compact and the tool is a fallback/refresh path, which is useful but not extensive. No side effects or additional behavioral caveats are disclosed, which is acceptable given the read-only annotation.

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 a single sentence that front-loads the core action and immediately provides usage conditions. There is no wasted text and the key advice about when to use the tool appears prominently.

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?

The description covers what the tool returns and when it should be invoked, and the schema covers all parameters. The lack of an output schema is a minor gap, but the trigger conditions and compactness make this sufficient for most selection and invocation decisions.

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 input schema fully documents all three parameters with descriptions and constraints, so the description does not need to add per-parameter detail. 'Compact recent session context' gives general intent but contributes little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and resource: 'Get compact recent session context', and adds a scoping condition. It does not explicitly distinguish itself from sibling tools such as knowl_context or knowl_state, so it is clear but not fully differentiated.

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 usage criteria: use it only when 'lifecycle bootstrap is unavailable (including manual mode)' or when an 'explicit refresh is needed'. It does not name alternative tools directly, but the when-to-use guidance is clear and actionable.

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