Skip to main content
Glama

AiAkiv Memory

by com.aiakiv
OverviewDiscussionsAdmin

search_partner_memory

Read-onlyIdempotent

Search a linked partner org's memory.

Use this when the user asks what a partner team has recorded about something.
Do not use it to search the caller's own memory; use `search_memory` for that.

Reads the partner org and writes nothing; a link is a read capability both
orgs agreed to rather than a project to switch into, so the caller's own scope
is untouched and `link_id` is passed per call. Results are the partner's
events and stay theirs. Calls are handled one at a time per org: a second link
call issued while one is in flight comes back with `reason: busy` without
running.

Args:
    sentence: One complete sentence, not keywords.
    link_id: Which link to read through, from `list_partner_links`.
    top_n: Max hits (server-capped at 50).
    domain: An optional single remote domain to narrow to.

Returns:
    `{status, link_id, remote_org, hits: [{event_id, domain, summary,
    timestamp, distance, link_id}], count}`. With `status="error"` the
    `reason` (`no_links`, `contract_version_too_old`, `busy`, ...) describes
    the state of the link, not a failure of the caller's own memory.
    `event_id` feeds `get_partner_memory_content`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_nNoMax hits (server-capped at 50).
domainNoAn optional single remote domain to narrow to.
link_idYesWhich link to read through, from `list_partner_links`.
sentenceYesOne complete sentence, not keywords.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds substantial behavioral context: the caller's scope is untouched, results remain the partner's, call concurrency is limited per org with a 'busy' reason, and error reasons describe link state rather than caller memory failures. This goes well beyond what the annotations alone convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loaded with the core purpose and usage guidance, followed by important behavioral details. The Args and Returns sections partially duplicate the input and output schemas, which costs a little efficiency, but the extra behavioral prose justifies the length overall.

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?

For a partner-memory search tool with concurrency constraints, error semantics, and ownership nuances, the description is remarkably complete. It covers when to use it, how it differs from the local-memory tool, what link_id means, how results are shaped, and how errors are interpreted. No critical operational detail is missing.

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 coverage is 100%, so the baseline is 3. The description's Args section largely restates the schema descriptions rather than adding new meaning. It does reinforce that sentence must be one complete sentence and that link_id is obtained from list_partner_links, but these appear in the schema as well, so no significant extra semantics are added.

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 opens with a specific verb and resource: 'Search a linked partner org's memory.' It distinguishes itself from search_memory by explicitly stating that search_memory is for the caller's own memory, making its scope unambiguous.

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?

It states exactly when to use the tool ('when the user asks what a partner team has recorded'), and explicitly says not to use it for the caller's own memory, pointing to search_memory as the alternative. It also mentions that link_id comes from list_partner_links, giving clear invocation context.

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

All AiAkiv Memory toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources