Skip to main content
Glama

memory_index

Read-only

Lists a project's stored memory titles and metadata with pagination to inventory existing entries, check for duplicates before writing, or retrieve a full index when a summary is truncated.

Instructions

枚举指定项目的记忆清单(只有标题与元数据,分页):盘点存量、写入前查重、或简报 truncated=true 时拉全量。响应始终返回 total(匹配总数,不是本页条数)与 next_offset;找具体内容仍用 memory_search。

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_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
sortNo排序,默认 updated
limitNo每页条数,默认 50,上限 500
scopeNo限定作用域层;默认 project 指定项目的全部(project/device/agent)
offsetNo分页偏移,默认 0
projectNo项目名或 id。省略时从当前工作目录自动解析

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavioral detail beyond that, namely that results contain titles and metadata but not content, and that responses always carry total and next_offset. It also flags the easy-to-misread semantics of total (all matches, not the current page). It stops short of covering rate limits or ordering guarantees, so it is strong but not exhaustive.

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?

A single compact passage, front-loaded with the core action and scope, then the use cases, then the response contract, then the sibling pointer. Every clause carries information; nothing is redundant with the title or schema.

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

Completeness5/5

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

For a six-parameter, zero-required, read-only listing tool with no output schema, the description supplies what is otherwise missing: the shape of the response, the pagination contract, and the fallback role when truncated=true appears. An agent has everything needed to call it correctly and to know when not to.

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

Parameters4/5

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

Schema coverage is already 83%, so the baseline is 3; the description earns above that by explaining pagination behavior through total and next_offset, which gives meaning to offset/limit beyond their schema text. It does not add anything for kind, sort, or scope, which is acceptable given the schema documents them.

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?

States a specific verb and resource (enumerate the memory index of a project) and immediately bounds the payload to titles and metadata with pagination. It explicitly contrasts with memory_search for content lookup, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives three concrete when-to-use cases: inventorying existing entries, dedupe checking before a write, and pulling the full set when a brief returns truncated=true. It also names the alternative (memory_search) for finding specific content, so both the positive and negative routing conditions are explicit.

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