Skip to main content
Glama

memory_preflight

Check memory before an action to surface past failures and return caution or block decisions, preventing repeated mistakes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for the action.
modeNoUnderlying capsule mode. Defaults to conservative.
toolNoTool or command family about to be used, e.g. Bash, npm test, Edit, deploy.
filesNoFile paths to fingerprint if record_event is true.
limitNoMax recall results to consider before preflight categorization.
scopeNoagent restricts memory recall to this server agent identity. shared searches the whole store. Defaults to agent.
actionYesNatural-language description of the action the agent is about to take.
strictNoIf true, high-severity memory warnings produce decision=block instead of caution.
session_idNoSession identifier for grouping the optional preflight event.
budget_charsNoCapsule budget in characters.
record_eventNoRecord a redacted PreToolUse event for this preflight. Defaults to false.
include_statusNoInclude memory health in the response and warning calculation. Defaults to true.
include_capsuleNoIf false, omit the embedded Memory Capsule from the response.
failure_window_hoursNoHow far back to check failed tool events. Defaults to 168 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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