Skip to main content
Glama
Sign In
shared-memory

shared-memory

by hina13140219-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

msg_send

Leave a message for another Claude window or all instances in a shared mailbox; recipients read it on demand, enabling handoffs without pushed notifications.

Instructions

Leave a message for another Claude window (shared mailbox). The recipient sees it only when it calls msg_read; nothing is pushed. "to" is the recipient's name, or "all" for everyone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>",
      "text": "<text>"
    },
    "name": "msg_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient name, or "all"
fromYesYour own name
textYesThe message: what the other side should do, where the files are
topicNoOptional category, e.g. handoff, version, task, chat. Handoff and version notes can be browsed later with msg_board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations to lean on, the description still discloses the non-obvious behavioral trait that governs this tool: delivery is pull-only, so the recipient will not be notified. It omits return-value behavior, failure modes (e.g. unknown recipient), and whether messages can be edited or recalled.

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?

Three tight sentences with the purpose front-loaded and delivery semantics before addressing details. The final sentence largely repeats the schema's own "to" description, costing a little efficiency.

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?

For a simple messaging tool with no annotations and no output schema, the description covers purpose, delivery model, and addressing adequately. It leaves minor gaps around return value and recipient-existence behavior that an agent might want.

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 description coverage is 100%, so all four parameters are already documented, including the "to" = name or "all" convention. The description merely restates the "to" semantics and adds no syntax, format, or constraint beyond the schema, so the baseline 3 applies.

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+resource ('Leave a message for another Claude window (shared mailbox)') and immediately distinguishes itself from the pull-based siblings by noting the recipient only sees it via msg_read. An agent can tell this apart from msg_read/msg_board without opening any 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?

Clearly frames the asynchronous delivery model ('nothing is pushed') and explains the addressing convention, which tells the agent when this communication channel is appropriate. It stops short of explicit when-not guidance or naming msg_board as the alternative for browsable notes (that hint lives only in the schema).

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