Skip to main content
Glama

Approve or reject a proposed project memory

playground_memory_proposal_review
Idempotent

Approve or reject one proposed memory note for this project, as the user would in Berrys. Approved notes are read by the Berrys agent on later turns; rejected ones are archived. External apps cannot approve memory proposals; the user must review them in Berrys.

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>",
      "proposalId": "<proposalId>",
      "decision": "<decision>"
    },
    "name": "playground_memory_proposal_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYesWhether to approve or reject the proposed memory; rejected notes are archived.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
proposalIdYesMemory proposal ID to review.

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
scopeYes
statusYes
contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The description usefully discloses downstream effects beyond the annotations: approved notes are read by the agent on later turns, rejected ones are archived, and it appears idempotent. However, the sentence "External apps cannot approve memory proposals; the user must review them in Berrys" conflicts with the tool's own purpose, leaving an agent unsure whether it is even permitted to call it — a real ambiguity that annotations do not resolve.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with the action front-loaded, but the final sentence is confusing and partially redundant with the opening "as the user would in Berrys" framing. That wording could be tightened or clarified to remove the apparent contradiction.

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?

Annotations and an output schema cover the safety profile and return shape, and the side effects are described. The main remaining gap is authority: an agent cannot tell definitively whether it may call this or must defer to the user in Berrys.

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% and includes a decision enum with its own description, so the schema carries the parameter burden. The description adds light value by scoping the tool to exactly one proposal in one project, though it adds no new detail on projectId or proposalId beyond the schema.

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 states a concrete verb pair plus the exact resource and scope: "Approve or reject one proposed memory note for this project." It is clearly distinct from sibling tools like playground_memory_propose (which creates proposals) and playground_memory_list (which reads them).

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 names the decision values and the effect of each, but gives no explicit when-to-use vs. sibling alternatives such as playground_memory_propose, and it never says which proposal ID source to consult. The closing sentence implies a user-in-the-loop prerequisite, but the phrasing is ambiguous rather than a clear precondition.

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.