Skip to main content
Glama
Sign In
contextforge-mcp

contextforge-mcp

by alfredoizdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_list_items

Read-onlyIdempotent

Lists stored memory items with titles, previews, tags, and dates so you can review and paginate saved notes across spaces.

Instructions

List all items stored in memory. Shows titles, previews, tags, and creation dates.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return (1-100, default: 50)
offsetNoNumber of items to skip (for pagination, default: 0)
space_idNoSpace UUID (optional, lists all spaces if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.15
  2. Removedv1.0.11
  3. Addedv1.0.4

TDQS

A3.5/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 description adds value by specifying the fields shown (titles, previews, tags, creation dates). However, it does not disclose pagination behavior or the default scope (all spaces unless space_id is specified as per schema).

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?

Two concise sentences with no redundancy: first states purpose, second states output fields. Every word is necessary.

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?

The description lists output fields but omits details like pagination limits or default ordering. Given no output schema, it is adequate but not fully comprehensive for a list tool.

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 100% with descriptions for all three parameters. The description does not add additional meaning beyond the schema, aligning with the baseline of 3.

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 'List all items stored in memory' with a specific verb and resource, and distinguishes itself from sibling tools like memory_list_projects by focusing on generic 'items' rather than projects or spaces.

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 provides no guidance on when to use this tool versus alternatives like memory_get_item or memory_query. It lacks any comparative context or usage scenarios.

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