Skip to main content
Glama

get_recall

Get a structured memory bundle for new tasks or cross-tool handoffs, including identity, recent activity, and relevant knowledge with governance metadata.

Instructions

获取结构化 Recall Surface v1 载荷。 / Get a structured Recall Surface v1 payload.

用途:在新任务、跨工具接续或需要"一次拿到可执行记忆包"时调用。
返回身份摘要、最近活动、项目/查询相关知识和治理元数据。
Purpose: Call when a new task or cross-tool handoff needs one structured,
actionable memory bundle: identity slice, recent activity, relevant
knowledge, and governance metadata.

注意:该聚合视图可能组合多类知识和最近上下文,因此治理开启时仅 owner
(private-self) 可读;非 owner 会在读取前被拒绝,不触发搜索或遥测写入。
Note: Because this aggregate view can combine multiple knowledge classes and
recent context, it is owner-only when governance is enabled. Non-owners are
refused before any search or telemetry side effect runs.

Args:
    project_folder: 项目文件夹路径(可选)。 / Project folder path (optional).
    query: 可选搜索焦点。 / Optional search focus.
    limit: 最多返回多少条知识(默认 8,上限 20)。 / Max knowledge items (default 8, max 20).
    token_budget: 知识片段的粗略 token 预算(默认 2000)。 / Rough token budget for knowledge items.
    include_freshness: 是否附加 freshness 提示。 / Attach freshness hints.
    collapse_versions: 是否折叠版本链到当前 HEAD。 / Collapse version chains to current heads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_folderNo
queryNo
limitNo
token_budgetNo
include_freshnessNo
collapse_versionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses owner-only behavior when governance enabled, non-owners refused before side effects, and composite nature. Lacks details on error handling or rate limits, but adequate for read tool.

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?

Structured with bold purpose, a critical note, then clear Args list. Bilingual but compact. Every sentence adds value; no redundancy or filler.

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?

Describes return content (identity, recent activity, knowledge, governance) and governance behavior. Output schema exists to detail return structure. Lacks explanation of parameter interactions (e.g., empty vs populated project_folder), but sufficient for an agent.

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 description coverage is 0%, but description adds meaningful semantics for all 6 parameters: purpose, defaults, and constraints (e.g., limit max 20, token_budget default). Could clarify boolean behavior (include_freshness, collapse_versions) further.

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 the tool retrieves a structured Recall Surface v1 payload combining identity, recent activity, knowledge, and governance metadata. Distinguishes from siblings by specifying composite nature and use for new task/handoff.

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?

Explicitly says when to use (new tasks, cross-tool handoff needing a single memory bundle). Could explicitly name alternatives (e.g., 'for just identity use get_identity_card'), but the purpose and sibling list provide implicit guidance.

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/Patdolitse/piia-engram'

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