Skip to main content
Glama

memory_observe_tool

Observe tool executions and store hashed, redacted metadata for memory and recall. Group events by session, track outcomes, and capture error summaries for audit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory at the time of the tool call
toolYesTool name being observed (Bash, Edit, Write, etc.)
eventYesHook event name (PreToolUse, PostToolUse, PostToolUseFailure, PreCompact, PostCompact, etc.)
filesNoFile paths to fingerprint (size + mtime + content hash)
inputNoTool input. Hashed and never stored raw; redacted metadata is only stored when retain_details is true.
outputNoTool output. Same redaction and storage policy as input.
outcomeNoOutcome classification
metadataNoArbitrary structured metadata (redacted before storage)
session_idNoSession identifier for grouping related events
error_summaryNoShort error description if the tool failed. Redacted and truncated to 2 KB.
retain_detailsNoIf true, redacted input and output payloads are stored alongside hashes. Defaults to false.

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.