Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

brain_predict

READ-ONLY — no side effects, no writes, no external network calls. Predictive Pre-fetch Engine (PPE): given your current context, reads the CKG in your Redis instance to predict likely failures and return the highest-confidence fixes. "Pre-load" means results are returned inline — nothing is cached or persisted. Requires a valid instance_id (your Redis brain). No rate limits. Call at session start when working on a specific feature or debugging area. Set scope="org" to widen prediction across your whole organisation — surfaces cross-team risks ("failed 3× across 2 other teams") from the Org Knowledge Graph, so an incident in one team becomes a vaccine for yours.

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": {
      "context": "<context>"
    },
    "name": "brain_predict"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoScope: "instance" (default) = this brain, "org" = warnings from failures in other teams of your organisation, "org+commons" = plus public lessons. Falls back to "instance" without an org.
top_kNoMax predictions to return (default: 5)
contextYesWhat you're working on, e.g. "upgrading Keycloak from 21 to 24"
instance_idNoBrain instance ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: read-only, no side effects, no writes, no external network calls, no rate limits, results returned inline and never cached or persisted, and a valid instance_id is required. The main gap is the response shape — what a "prediction" or "fix" record actually contains is never described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The safety profile is front-loaded in the first clause, and the remainder is mostly load-bearing. Some phrasing is promotional ("an incident in one team becomes a vaccine for yours") and the explicit gloss on "Pre-load" is slightly redundant, but nothing is truly wasted.

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?

For a four-parameter, single-required-field tool with full schema coverage and no output schema, the definition covers safety, auth prerequisite, rate limits, invocation timing, and scope trade-offs. The one missing piece an agent would want is what the returned predictions look like and how confidence is expressed.

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 description coverage is 100%, so all four parameters are already documented, including the scope enum and its fallback behavior. The description reinforces the org-scope value proposition ("cross-team risks", "failed 3× across 2 other teams") and clarifies that instance_id is the Redis brain, but adds little syntax or meaning the schema does not already carry.

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 states a specific verb and resource: it reads the CKG in your Redis instance to predict likely failures and return highest-confidence fixes. That is concrete enough for an agent to distinguish it from retrieval-style siblings such as brain_search or recall_best_solution. It does not explicitly name any sibling as an alternative, which keeps it short of a 5.

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?

It gives a clear trigger: "Call at session start when working on a specific feature or debugging area", and explains the scope="org" variant for cross-team risks. There is no explicit when-not guidance or named alternative tool, so an agent must infer the boundary against recall/smart_recall style siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.