Skip to main content
Glama
Sign In
agent-knowledge

agent-knowledge

by yucx-go
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ak_dream

Run a dream cycle to consolidate recent sources into long-term memory, processing data from the last N hours to improve knowledge retrieval and recall.

Instructions

Run a dream cycle (memory consolidation) over recent sources.

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

Input Schema

NameRequiredDescriptionDefault
since_hoursNoProcess sources from last N hours (default: 24).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'Run' implies a state-changing action, but lacks details on side effects, prerequisites, idempotency, or what the result is. The '(memory consolidation)' gives some context but not enough.

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, front-loaded sentence that efficiently conveys the core action and scope. There is no redundant information, and it is appropriately sized for a simple one-parameter tool.

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?

For a simple tool with one parameter and no output schema, the description is adequate but not complete. It lacks details about the outcome of running a dream cycle, any prerequisites (e.g., having ingested sources), or expected return values. The schema covers the parameter, but behavioral completeness is missing.

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 covers 100% of the parameter (since_hours) with a clear description and default. The phrase 'recent sources' in the tool description loosely maps to this parameter, reinforcing it but adding no new syntax or format details. Baseline 3 is appropriate.

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 clearly states the verb 'Run' and the resource 'dream cycle' with an explanatory parenthetical '(memory consolidation)'. It distinguishes from siblings like ak_query and ak_ingest by describing a unique operation, though it doesn't explicitly contrast with them.

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

Usage Guidelines3/5

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

Usage context is implied by mentioning 'recent sources', suggesting it pairs with ingesting data, but there is no explicit guidance on when to use this tool versus alternatives. The description doesn't provide exclusions or when-not-to-use conditions.

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