Skip to main content
Glama
Sign In

memory

by com.borisinc
OverviewDiscussionsAdmin

memory_search_free

FREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign. Same wallet_auth scheme as memory_write_free. Capped at 500 searches / rolling 30 days per wallet.

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": {
      "query": "<query>",
      "wallet_auth": "<wallet_auth>"
    },
    "name": "memory_search_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNomax results (default 5, cap 20)
queryYes
wallet_authYesbase64 JSON {address,ts,signature}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Discloses free tier, cap, and auth scheme, but no annotations exist. Does not state if operation is read-only or has side effects, nor behavior when cap is exceeded.

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?

Two concise sentences with key information front-loaded. No extraneous text.

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?

Explains auth and cap, but lacks details on return format or error handling. Adequate for a simple search tool, but could be more complete given no output schema.

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 covers 67% of parameters (k and wallet_auth have descriptions). Description does not add beyond schema; query parameter lacks description in both schema and description.

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?

Clearly states it's a free semantic search over the user's namespace with wallet authentication. Distinguishes from sibling tools like memory_search (paid) and memory_write_free (same auth scheme).

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

Usage Guidelines4/5

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

Indicates free tier with cap of 500 searches per 30 days, implying use for limited queries. References same auth as memory_write_free, but lacks explicit when-to-use vs memory_search or when-to-avoid.

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

All memory toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources