Skip to main content
Glama
Sign In
Memento

Memento

by JoyciAkira
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memento_code

Inspect code symbol graphs and link grounded memories to symbols or files, then view index statistics. Use it to verify how agent memories relate to code structure.

Instructions

Inspect the code symbol index and memory grounding. Actions: graph, links, stats.

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": {
      "action": "<action>"
    },
    "name": "memento_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoWorkspace-relative file for graph.
limitNoMax nodes, edges, or memories to return.
queryNoFind grounded memories by symbol or path for links.
actionYesAction to perform.
symbolNoSymbol name for graph.
memory_idNoMemory ID for links.
workspace_rootNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.2

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Inspect" implies reads, but it does not say whether the index is cached or stale, how expensive a graph traversal is, whether results are truncated by the limit default, or what any action returns.

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?

Two short sentences, front-loaded with purpose followed by the action list. No filler, though the terseness borders on under-specification for a 7-parameter multi-action tool.

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?

With no annotations and no output schema, a three-action tool with 7 parameters needs the description to explain what each action produces and how parameters bind to actions. The description lists action names only, leaving an agent unable to predict results or pick correct parameters per action.

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 coverage is 86%, so the input schema already documents file, limit, query, symbol, memory_id and the action enum with per-action hints. The description adds nothing to those semantics, so the baseline 3 applies rather than a bonus.

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

Purpose3/5

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

"Inspect the code symbol index and memory grounding" states a verb (inspect) and two resources, and names the three actions (graph, links, stats). However, it does not distinguish this from siblings like memento_kg or memento_graph, and the relationship between the three actions and the two resources is left for the agent to infer.

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 lists the valid actions but gives no guidance on when to choose graph vs links vs stats, nor any context on alternatives among the many sibling tools. An agent must read the parameter schema and guess at intent.

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