Skip to main content
Glama

Read approved Playground project memory

playground_memory_list
Read-onlyIdempotent

Read approved project-shared memory and this user’s private memory. Requires project view access. Returns the project’s available memories.

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": {
      "projectId": "<projectId>"
    },
    "name": "playground_memory_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
memoriesYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two things not in the structured data: an authorization prerequisite ('Requires project view access') and the scope caveat that only approved project memory plus the caller's private memory are returned, which implies pending proposals are excluded.

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?

Three short sentences with the scope stated first and the access requirement second. The final sentence ('Returns the project's available memories') largely restates the opening scope and could be dropped, but overall there is no padding.

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

Completeness4/5

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

For a single-parameter, non-destructive read with an output schema, the description covers scope, access requirement, and return intent. The one remaining gap is how it relates to the sibling read/search memory tools, which the agent must guess.

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?

Only one parameter exists and schema description coverage is 100%, including a UUID pattern and guidance on where to obtain the project ID. The description adds nothing about projectId, which is acceptable at this coverage level but leaves the baseline.

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?

States a specific verb and resource ('Read approved project-shared memory and this user's private memory'), and scopes it beyond a generic memory read by naming two distinct visibility tiers. It does not explicitly contrast with siblings like playground_memory_search or playground_memory_propose, so the agent must infer the boundary from the word 'approved'.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can tell this is the read/list path for already-approved memory, and the access prerequisite ('Requires project view access') is a useful gate. There is no explicit statement of when to use this versus playground_memory_search for retrieval or playground_memory_propose for adding memory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.