Skip to main content
Glama
LamantinAI

kaeru memory

by LamantinAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

link_cloud

Creates a soft reference from an agent memory record to a cloud record, enabling local decisions and tasks to point to external cloud entries.

Instructions

Create a soft reference to a cloud record.

Input Schema

NameRequiredDescriptionDefault
nameYes
cloudNo
cloud_idYes
edge_typeNo
initiativeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 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: -"Cloud the dst lives in (multi-cloud). Omit for the default cloud — the\nsoft link records the name so resolution routes to the right endpoint."
    • addedInput schema / properties / cloud / minLength
      Added value: +1
    • changedInput schema / properties / cloud / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / cloud_id / description
      Removed value: -"UUIDv7 id of the cloud node to link to."
    • addedInput schema / properties / cloud_id / minLength
      Added value: +1
    • removedInput schema / properties / edge_type / default
      Removed value: -null
    • removedInput schema / properties / edge_type / description
      Removed value: -"Edge type for the soft link — closed vocabulary, one of: `refers_to` (default), `causal`, `derived_from`, `contradicts`, `part_of`, `blocks`, `targets`, `supersedes`, `verifies`, `falsifies`, `temporal`, `consolidated_to`."
    • changedInput schema / properties / edge_type / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedInput schema / properties / initiative / description
      Removed value: -"Initiative scope (both sides share the same initiative name)."
    • addedInput schema / properties / initiative / minLength
      Added value: +1
    • removedInput schema / properties / name / description
      Removed value: -"Local node name or UUIDv7 id to soft-link from."
    • addedInput schema / properties / name / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "cloud_id",
-  "initiative"
-]New value: +[
+  "initiative",
+  "name",
+  "cloud_id"
+]
    • removedInput schema / title
      Removed value: -"LinkCloudParams"
  2. First observedv0.7.5

TDQS

C2.4/5.0
Behavior2/5

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

The annotation readOnlyHint=false already establishes that this is a mutation, and the description consistently says 'Create.' It adds the notion of a 'soft reference' but does not explain what that means operationally, whether duplicates are allowed, what permissions are required, or what side effects occur.

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?

A single front-loaded sentence with no wasted text. It is concise, though its brevity reflects under-specification rather than efficient completeness.

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

Completeness1/5

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

For a five-parameter mutation tool with no output schema, 0% schema description coverage, and only a minimal readOnlyHint annotation, one short sentence is not enough. It leaves required parameter semantics and creation behavior undocumented.

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

Parameters1/5

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

Schema description coverage is 0% across five parameters, and the description mentions none of them. It does not clarify required fields such as initiative, name, cloud_id, or the distinction between cloud and cloud_id, so it provides no parameter meaning beyond the bare schema.

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?

States a specific verb and resource: 'Create a soft reference to a cloud record.' This is more than a tautology, but 'soft reference' is domain jargon and the description does not distinguish this tool from siblings such as cloud_links, share, or reference.

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?

Gives no guidance on when to use this tool versus alternatives like cloud_links, share, or unshare. It only implies creation, with no prerequisites, exclusions, or routing context.

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