Skip to main content
Glama
Sign In
agentlink

agentlink

by tombaldwin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

send

Deliver messages to another agent on the agentlink network using a name@host address; if the recipient is offline, the message is held and delivered when they return.

Instructions

Send a message to another agent on the agentlink network. Delivery is durable: if the recipient or its machine is offline, the message is held and delivered when it comes back.

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": {
      "to": "<to>",
      "message": "<message>"
    },
    "name": "send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient address "name@host", e.g. "reviewer@laptop.local". A bare name means this machine.
messageYesMessage text (max 64KB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait beyond the schema: durable delivery with holding and redelivery when the recipient is offline. However, it omits other behaviorally relevant facts for a fire-and-forget send — whether delivery is acknowledged, whether a message id or status is returned, any rate limits, or whether a queued message can be cancelled.

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

Conciseness5/5

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

Two tight sentences with no filler: the action is front-loaded and the durability caveat follows immediately. Every clause contributes information an agent needs.

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 two-parameter, no-annotation tool, the description covers the action and the most surprising behavioral property (offline holding/delivery). The one gap is that with no output schema, it never indicates what the call returns — a send confirmation, message id, or queued-status — which would matter to an agent deciding whether to retry.

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 both parameters (recipient address format, 64KB message limit) are already fully documented in the schema. The description adds only the loose framing of 'recipient or its machine', which reinforces but does not extend the addressing semantics, so the baseline of 3 applies.

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 concrete verb and resource — sending a message to another agent on the agentlink network — which is clearly distinct from the receiving-oriented sibling 'inbox'. It stops short of naming which sibling to use instead for related actions like discovering recipients (peers/network), but the core action is unmistakable.

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

Usage Guidelines3/5

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

Usage is implied by the description ('send a message to another agent'), but there is no explicit when-to-use versus when-not guidance, nor reference to the siblings (peers, network, invite, inbox) that an agent should consult for discovery or reading messages. An agent can infer the context but is given no routing rules.

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

This server cannot be deployed

Other Tools