Skip to main content
Glama
farena-ai

Sara

by farena-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search her memory

search_memory
Read-onlyIdempotent

Search the owner's long-term memory by words and meaning to retrieve facts, past conversation summaries, decisions, promises, and dates for context about their life, preferences, and projects.

Instructions

Search Sara's long-term memory about the owner (facts, summaries of past conversations, decisions, promises, dates) by words and meaning. Use it for context about the owner's life, preferences and projects; use list_facts to browse all facts, search_library for documents, and list_recent_conversations for what was talked about lately. Returns plain text, one note per line: "- [kind, YYYY-MM-DD] text", best match first, or a line saying nothing was found. Read-only. Never includes other people's chats, private conversations or (while Adult mode is off) anything explicit.

Input Schema

NameRequiredDescriptionDefault
limitNoMost notes to return, 1 to 50 (default 10).
queryYesWords to look for in her memory. Up to 200 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Up to how many notes (default 10)."New value: +"Most notes to return, 1 to 50 (default 10)."
    • addedInput schema / properties / limit / examples
      Added value: +[
+  10
+]
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for, e.g. \"sister\" or \"deploy server\"."New value: +"Words to look for in her memory. Up to 200 characters."
    • addedInput schema / properties / query / examples
      Added value: +[
+  "sister",
+  "deploy server",
+  "favourite food"
+]
    • addedInput schema / properties / query / maxLength
      Added value: +200
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover safety (readOnlyHint, idempotent, non-destructive), but the description adds substantial behavior: exact return format ('- [kind, YYYY-MM-DD] text'), ordering (best match first), the empty-result sentinel line, and content exclusions (other people's chats, private conversations, explicit content while Adult mode is off). These are things the annotations cannot express.

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?

Four sentences, all load-bearing, with the core purpose front-loaded and alternatives and return format following in logical order. No filler or restatement of the name/title.

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?

With no output schema, the description still specifies the return format, ordering and empty-result case, and it discloses privacy boundaries. An agent has everything needed to call this correctly and interpret the result.

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%, so the baseline is 3; the description earns extra credit by clarifying the query is matched 'by words and meaning' (keyword plus semantic), which the schema's examples alone do not convey. It does not discuss the limit parameter, but the schema documents that fully.

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?

States a specific verb (search) plus resource scope ('Sara's long-term memory about the owner') and enumerates the content kinds (facts, summaries, decisions, promises, dates). It also names the sibling tools it is not (list_facts, search_library, list_recent_conversations), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('for context about the owner's life, preferences and projects') and routes the caller to the right alternative for each other need (browse all facts → list_facts, documents → search_library, recent chatter → list_recent_conversations). Both positive and exclusionary guidance are present.

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

Deploy Server

Other Tools