Skip to main content
Glama

memory

by com.borisinc

memory_write_free

FREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment. wallet_auth = base64 JSON {address,ts,signature} where signature = personal_sign of 'borismem-free::' (ts within 600s). Writes to the SAME namespace paid calls use. Capped at 1000 writes / rolling 30 days per wallet; over cap returns an error pointing to the paid tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
contentYesThe memory text (max 8000 chars)
wallet_authYesbase64 JSON {address,ts,signature} -- see description

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: free tier, auth mechanism, namespace sharing, write cap (1000/30 days), and error behavior.

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?

Three dense sentences with zero waste, front-loaded with 'FREE (no payment)' for quick understanding.

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

Completeness5/5

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

Covers purpose, auth, namespace, rate limits, and error handling. No output schema exists, so return value omission is acceptable. Complete for a free write tool.

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?

The description adds significant detail for wallet_auth (format, signing scheme, timestamp constraint) beyond the schema. Tags lack schema description but description doesn't expand it; overall good compensation.

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 clearly states the tool stores a memory using a free auth method (EIP-191 personal_sign) instead of payment, distinguishing it from the paid tier.

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?

It explains this is the free alternative to paid calls, mentions the cap and error redirection, but does not explicitly list alternative tools or when-not-to-use scenarios beyond the cap.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: export, forget, import, search (paid/free), stats, write (paid/free). No functional overlap.

Naming Consistency5/5

All tools follow the 'memory_<verb>' pattern, with free variants appending '_free'. Consistent and predictable.

Tool Count5/5

8 tools is well-scoped for a memory server, covering essential operations without unnecessary bloat.

Completeness4/5

Covers CRUD via write (with supersede), search, export, forget, import, and stats. Missing a direct get-by-id tool, but export and search suffice.

Resources