Skip to main content
Glama
Sign In
ai-dememory

ai-dememory

by GonzaloTorreras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Hook Events

memory.hook_events
Read-only

Returns supported hook events for local providers like codex and claude to enable event-driven memory updates.

Instructions

Return supported local provider hook events.

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": "memory.hook_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault
providersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. The description adds 'local provider' context but no further behavioral traits like pagination, caching, or scope of returned events.

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 description is very brief with no wasted words. Structure could be improved by adding a brief note on the parameter, but overall it is efficient.

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

Completeness2/5

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

Given the presence of an output schema and annotations, the description is too minimal. It does not explain what hook events are, the output format, or how the optional parameter changes results.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the 'provider' parameter. It does not. The parameter has enum values but their meaning (filter by provider, null for all) is not clarified.

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 states the tool returns supported local provider hook events, using a specific verb and resource. It distinguishes from sibling tools like memory.hook_config and memory.hook_status which deal with configuration and status, not events.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or context for querying hook events.

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