Skip to main content
Glama

Record Recall Eval Judgment

record_recall_eval_judgment

Record whether a recalled memory was relevant to a query for evaluation purposes. Use to assess and improve memory retrieval quality.

Instructions

Evaluation only — record whether a returned memory was relevant for a query. Do not use in normal conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language question or search text.
reasonNoOptional user-facing reason for the deletion.
positionNoOne-based rank position of the memory in the recall results, or 0 if not returned.
relevantYesWhether the memory was relevant to the recall-evaluation query.
memory_idYesExact XMemo memory reference shown by search or recall.
metadata_jsonNoOptional JSON object string with extra metadata for the operation.{}
expected_relevant_totalNoExpected number of relevant memories for this recall-evaluation query.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations are provided, so the description's burden is lower. It adds the behavioral context that this is evaluation-only and records relevance. It does not disclose details about side effects or authentication needs, but it does not contradict annotations.

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?

The description is extremely concise with two short sentences. It front-loads the essential constraint 'Evaluation only' and immediately clarifies purpose and usage restriction.

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?

Given the output schema exists and the tool has a clear eval purpose, the description covers the core functionality adequately. It could briefly mention integration with run_recall_eval, but for the scope, it is fairly complete.

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%, so the description adds minimal meaning beyond the schema. It implicitly references 'query', 'memory_id', and 'relevant' but does not provide additional parameter semantics. Baseline score of 3 is appropriate.

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 it is for evaluation only, recording relevance of a returned memory for a query. It explicitly contrasts with normal conversation, distinguishing its purpose from sibling tools like record_recall_feedback.

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?

The description provides explicit guidance: 'Do not use in normal conversation' and 'Evaluation only'. This clearly indicates when to use (during recall evaluation) and when not to. It does not name specific alternatives but the context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonro/memory-os-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server