Skip to main content
Glama
deenesjakoruzh
wmt-mobile

LocalNest MCP

by wmt-mobile
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Memory Events

localnest_memory_events
Read-onlyIdempotent

List recent memory events and track their promotion status to durable memory for local AI agent projects.

Instructions

List recently captured memory events and whether they were promoted into durable memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathNo
limitNo
offsetNo
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • src/mcp/tools/memory-store.js:221-227 (handler)
    The handler function for the localnest_memory_events tool, which calls memory.listEvents and normalizes the result.
    async ({ project_path, limit, offset }) => normalizeMemoryEventsResult(
  await memory.listEvents({
    projectPath: project_path,
    limit,
    offset
  })
)
  • src/mcp/tools/memory-store.js:204-228 (registration)
    Registration of the localnest_memory_events tool.
    registerJsonTool(
  ['localnest_memory_events'],
  {
    title: 'Memory Events',
    description: 'List recently captured memory events and whether they were promoted into durable memory.',
    inputSchema: {
      project_path: z.string().optional(),
      limit: z.number().int().min(1).max(200).default(20),
      offset: z.number().int().min(0).default(0)
    },
    annotations: {
      readOnlyHint: true,
      destructiveHint: false,
      idempotentHint: true,
      openWorldHint: false
    }
  },
  async ({ project_path, limit, offset }) => normalizeMemoryEventsResult(
    await memory.listEvents({
      projectPath: project_path,
      limit,
      offset
    })
  )
);

Tool Definition Quality

B3.3/5.0
Behavior4/5

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

While annotations declare read-only/idempotent safety, the description adds valuable domain context about the 'promotion' lifecycle (captured events vs. durable memory) that annotations cannot convey. It does not contradict the safety annotations and adds conceptual clarity.

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?

The description is a single, dense sentence of 12 words with zero redundancy. It front-loads the action ('List') and packs domain-specific detail ('promoted into durable memory') efficiently.

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

Completeness3/5

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

Given the existence of an output schema, the description appropriately omits return value details. However, for a 4-parameter tool with zero schema documentation, the description should have included parameter semantics to be complete. It adequately covers the core operation but leaves significant gaps.

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?

With 0% schema description coverage across 4 parameters, the description fails to compensate. Critical parameters like 'project_path' are left completely undocumented, and while 'limit'/'offset' may be self-evident, the description adds zero semantic value beyond the parameter names.

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 uses specific verb 'List' and resource 'memory events', and adds crucial domain detail about 'promoted into durable memory'. However, it does not explicitly differentiate from siblings like 'localnest_memory_list' or 'localnest_memory_capture_event', leaving ambiguity about when to query events vs. durable memory.

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?

The description implies a temporal scope with 'recently captured' but provides no explicit guidance on when to use this tool versus the 5+ sibling memory tools (e.g., localnest_memory_list, localnest_memory_capture_event). No prerequisites or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wmt-mobile/localnest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server