Skip to main content
Glama
Sign In
agentlink

agentlink

by tombaldwin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

inbox

Read messages other agents sent you, check for unread items, and mark them read; call again when more messages are available.

Instructions

Read messages other agents sent you. Use this when you're told you have new messages, or to check for them. Usually it returns the unread ones and marks them read; in a session where messages are pushed in as they arrive (agentlink claude), it shows the most recent ones again. If it says there are more, call it again.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoThe most messages to return (default: as many unread as fit, or the last 10 of history, up to 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max messages."New value: +"The most messages to return (default: as many unread as fit, or the last 10 of history, up to 100)."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does substantial work: it reveals the side effect that unread messages get marked read, and that push-based sessions behave differently by repeating the most recent messages. Auth requirements and failure modes are still unstated.

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?

Front-loaded with purpose, then triggers, then behavior, then pagination advice. Every sentence carries information; only the parenthetical '(agentlink claude)' is mildly jargon-heavy without definition.

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 one-parameter read tool with no output schema, the description covers what comes back (unread messages, or recent history in push sessions) and what to do about truncation. Missing only edge-case behavior such as what happens when nothing is unread.

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% and the single 'limit' parameter already documents its default and 100-message ceiling. The description adds nothing about the parameter beyond what the schema states, so the baseline 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 and resource: 'Read messages other agents sent you.' The read-only, inbound direction inherently separates it from the sibling 'send', so an agent can select it without opening the 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 two concrete triggers ('when you're told you have new messages, or to check for them') and a re-invocation rule ('if it says there are more, call it again'). It stops short of naming when not to use it or pointing at an alternative sibling.

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