Skip to main content
Glama
Sign In
MemAI

MemAI

by Filipe-Soares-de-Almeida
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

also_domain

Idempotent

Cross-list a memory into an additional domain path so it appears in that domain's reads without moving it.

Instructions

Cross-list an existing memory into one more domain path.

For the membership a memory picks up after the fact: it was filed where it lives, and later turns out to be part of a subject that cuts across the tree. Every read scoped to domain returns it from now on, without moving it -- use the dashboard's re-home for that.

Returns {"uid": ..., "also": [...]} with the whole resulting set. A path the memory's own domain already sits under is dropped as redundant, so the echo is what actually holds.

Input Schema

NameRequiredDescriptionDefault
uidYesthe memory.
domainYesthe path to cross-list it into.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.1
    • addedInput schema / properties / domain / description
      Added value: +"the path to cross-list it into."
    • removedInput schema / properties / domain / title
      Removed value: -"Domain"
    • addedInput schema / properties / uid / description
      Added value: +"the memory."
    • removedInput schema / properties / uid / title
      Removed value: -"Uid"
    • removedInput schema / title
      Removed value: -"also_domainArguments"
  2. Addedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

With annotations only declaring write/idempotent/non-destructive, the description carries real weight: it discloses the durable effect (every read scoped to `domain` returns it), that nothing is moved, the return shape, and the dedup rule that a redundant ancestor path is dropped. This is behavior an agent cannot infer from the annotations.

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 action is front-loaded in the first sentence and the rest elaborates behavior. Slightly prose-y and indirect in places ('the echo is what actually holds'), but every clause contributes information rather than filler.

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?

Though there is no output schema, the description spells out the return shape ({uid, also: [...]}) and the dedup semantics, covering both the call and its result for a simple two-parameter 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?

Schema coverage is 100% so the baseline is 3, but the description adds semantic depth: `domain` is a path in a tree, and paths already subsumed by the memory's own domain are silently dropped. That redundancy rule is meaning beyond the schema's one-line description.

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 and resource ('cross-list an existing memory into one more domain path') and immediately distinguishes the semantics from moving ('without moving it -- use the dashboard's re-home for that'). An agent can tell this apart from move_to_project or unfile_domain without opening a schema.

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?

Gives a concrete when-to-use scenario: a memory filed elsewhere that later proves to belong to a cross-cutting subject. It also carves out when NOT to use it (re-homing/moving) by pointing at the dashboard. No sibling tool is named as an alternative, so it stops short of a 5.

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