Skip to main content
Glama

Remember a Playground project note

playground_memory_propose

Remember a user decision or verified project fact, with optional source node citations. It takes effect immediately: the Playground agent reads remembered notes in every later turn, the same way it remembers what users tell it. Requires project edit access.

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>",
      "scope": "<scope>",
      "kind": "<kind>",
      "content": "<content>"
    },
    "name": "playground_memory_propose"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesMemory category used to organize the proposed guidance.
scopeYesScope in which to find or save the requested item.
contentYesMemory text to propose for future creative work.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
sourceNodeIdsNoCanvas node IDs that provide evidence for the proposed memory.

Output Schema

NameRequiredDescriptionDefault
idYes
scopeYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the note takes effect immediately and is read by the Playground agent in every later turn. It also states the project edit-access requirement. It stops short of explaining editability or retraction of remembered notes, but the core side effect is well surfaced.

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?

The description is three tight sentences with the purpose, immediate effect, and access prerequisite front-loaded. There is no wasted wording, and the persistence consequence is stated before the prerequisite.

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?

With full schema coverage, annotations, and an output schema, the description is largely complete for a five-parameter mutation tool. The main missing context is how this relates to the sibling proposal-review workflow, especially given the tension between 'propose' and 'takes effect immediately.'

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 description coverage is 100%, so the schema already documents projectId, scope, kind, content, and sourceNodeIds. The description adds only the phrase 'optional source node citations,' which maps to sourceNodeIds but does not add syntax or selection guidance beyond the schema.

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?

The description states a specific verb and resource: remember a user decision or verified project fact, with optional source citations. It is clear enough to distinguish from memory search/list tools, but it does not reconcile the tool name 'propose' with the claim that the note takes effect immediately.

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?

It implies when to use the tool by limiting it to user decisions and verified project facts, and it notes the edit-access prerequisite. However, it does not explicitly compare against siblings such as memory_list, memory_search, or memory_proposal_review, so the agent must infer the boundaries.

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.