Skip to main content
Glama
LamantinAI

kaeru memory

by LamantinAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

pull

Copy a cloud node into a local initiative to sync remote memory into the agent’s local graph.

Instructions

Copy one cloud node into the local initiative.

Input Schema

NameRequiredDescriptionDefault
idYes
cloudNo
initiativeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / cloud / default
      Removed value: -null
    • removedInput schema / properties / cloud / description
      Removed value: -"Source cloud name in a multi-cloud setup. Omit for the default cloud."
    • addedInput schema / properties / cloud / minLength
      Added value: +1
    • changedInput schema / properties / cloud / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / id / description
      Removed value: -"UUIDv7 id of the cloud node to materialise into the local vault."
    • addedInput schema / properties / id / minLength
      Added value: +1
    • removedInput schema / properties / initiative / description
      Removed value: -"Initiative to attach the pulled node to locally."
    • addedInput schema / properties / initiative / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "initiative"
-]New value: +[
+  "initiative",
+  "id"
+]
    • removedInput schema / title
      Removed value: -"PullParams"
  2. First observedv0.7.5

TDQS

C2.7/5.0
Behavior2/5

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

The description is consistent with readOnlyHint=false because it describes a copy into the local initiative, which implies mutation. However, it does not disclose important behavioral details such as whether an existing local node is overwritten, what permissions are required, or whether the operation is idempotent.

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 a single front-loaded sentence with no wasted words. Its brevity is appropriate structurally, though it contributes to the surrounding completeness gaps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no output schema and minimal annotation detail, the description is too thin. It identifies the broad action but omits parameter semantics, side effects, and selection guidance among many related cloud and link tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It hints that 'id' identifies the cloud node and 'initiative' is the local target, but the optional 'cloud' parameter is completely unexplained, and no format or default information is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Copy one cloud node into the local initiative.' It clearly distinguishes a copy action from a link action, but it does not explicitly differentiate itself from close siblings such as cloud_recall, link_cloud, or sync_review.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, prerequisites, or alternatives. It implies a copy operation but does not tell the agent when to choose this over related tools like link_cloud or cloud_recall.

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