Connapse

Overview Schema Source Related Servers Discussions Admin

memory_spaces

Read-onlyIdempotent

List available personal and team memory spaces with IDs and permissions to select the correct destination before saving a memory; optionally filter by kind or name.

Instructions

List the memory spaces you can use: your personal spaces (only you see them) and team spaces (everyone in this Connapse sees them). Each comes with its id, name, kind, description, whether you can add to it, and who sees it. Call this before saving to pick a space for memory_remember; if none fits, make one with memory_space_create. At most 100 are returned; pass name to find others.

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

Input Schema

Name	Required	Description	Default
`kind`	No	Only this kind: "personal" or "team"
`name`	No	Only spaces whose name or description contains this text

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Nov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint), and the description adds real behavior on top: visibility semantics for personal versus team spaces, the shape of each returned record including whether the caller can add to it, and a hard result cap of 100 with a filtering workaround. That is context an agent could not infer from the annotations.

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?

Three sentences, front-loaded with what the tool returns, then when to call it, then the limit and escape hatch. Every sentence carries distinct information; nothing is repeated from the schema verbatim.

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?

There is no output schema, so the description carries the return-value burden and does so by listing the fields of each space. Combined with the cap, the filtering workaround, and the routing to memory_remember and memory_space_create, an agent has everything needed to call and act on this tool.

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 100%, so both parameters are already documented, and the description still adds the motivating use case for `name` — locating spaces beyond the 100-result cap rather than just substring matching. The `kind` parameter is not discussed in the description, but the personal/team distinction in the opening sentence effectively maps onto it.

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?

Opens with a specific verb and resource ("List the memory spaces you can use") and immediately splits the resource into its two kinds, personal and team, with the visibility difference spelled out. It also enumerates the returned fields, so an agent knows exactly what this call yields without opening the 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 an explicit trigger ("Call this before saving to pick a `space` for memory_remember") and an explicit fallback alternative ("if none fits, make one with memory_space_create"). It also supplies a recovery path when the result set is capped: pass `name` to find others.

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