Skip to main content
Glama

Search Playground project memory

playground_memory_search
Read-onlyIdempotent

Search approved project-shared memory and this user’s private memory by words in their content, with offset/limit pagination. Requires the memory:read grant. Returns matching memories, total count and next-page offset.

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>",
      "query": "<query>"
    },
    "name": "playground_memory_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return in this page.
queryYesSearch words describing the item or content to find.
offsetNoNumber of matching results to skip; use the previous response’s nextOffset for another page.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
totalYes
memoriesYes
nextOffsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's real addition is the 'Requires the memory:read grant' auth prerequisite and the pagination/return-shape note, which is useful context beyond the annotations but not deep — no ranking, matching-tokenization, or empty-result behavior is disclosed.

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 tight sentences, front-loaded with the resource scope, followed by the auth prerequisite and the return contract. No filler or restatement of the title; the only slight redundancy is naming offset/limit pagination and then the next-page offset again.

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 an output schema present, the description needn't detail return fields, and it still names the key ones (memories, total count, next-page offset) plus the required grant. For a four-parameter read tool this covers what an agent needs to invoke it correctly, with only the alternative-tool routing left open.

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% with all four parameters individually documented, including the nextOffset continuation hint, so the schema already carries the semantics. The description adds only the phrase 'words in their content' to characterize the query and confirms offset/limit paging, which is marginal value over the structured fields.

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 (search) plus the exact resource scope: approved project-shared memory and the calling user's private memory, matched on words in content. The scope contrast implicitly separates it from a plain listing tool, but no sibling (e.g. playground_memory_list) is named, so differentiation is inferred rather than explicit.

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 implied by the mechanism ('by words in their content'), which suggests keyword lookup rather than enumeration, and the pagination note hints at result-set traversal. However, there is no explicit statement of when to choose this over playground_memory_list or the propose/review tools, and no when-not guidance.

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.