Skip to main content
Glama
Sign In
Cachly — AI Cognitive Brain

Cachly — AI Cognitive Brain

by cachly-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cache_stream_get

Retrieve a previously cached stream as an ordered list of string chunks. Returns null on cache miss to handle missing keys.

Instructions

Retrieve a previously cached stream as an ordered list of string chunks. Returns null on cache miss (key absent or empty list). Stored under cachly:stream:{key}.

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": {
      "instance_id": "<instance_id>",
      "key": "<key>"
    },
    "name": "cache_stream_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesCache key
instance_idYesUUID of the cache instance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It correctly states the return value on cache miss (null) and the storage key format, but omits details like read-only nature, error conditions, or performance characteristics.

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 lean sentences with no wasted words. The action verb and outcome are front-loaded, making it easy for an agent to quickly grasp the tool's function.

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?

Given the absence of an output schema, the description adequately explains the return value and its structure (ordered list of string chunks, null on miss). It covers the main use case but could mention potential error scenarios beyond cache miss.

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

Parameters4/5

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

Schema covers both parameters (100%). The description adds value by revealing the key format ('cachly:stream:{key}'), which helps the agent form correct key values beyond the schema's generic 'Cache key' description.

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 clearly specifies the verb 'Retrieve' and the resource 'previously cached stream as an ordered list of string chunks'. It distinctly separates this from sibling cache tools like cache_get (single value) and cache_stream_set (write operation).

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?

The description implies it is used for reading a stream of chunks, but does not explicitly state when to use it versus alternatives like cache_get or cache_mget. No exclusion criteria or use-case guidance is provided.

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