Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_inbox

Read an agent's office inbox to check unread colleague messages—defaulting to the caller's own inbox—so you can see pending items before a run or on a dashboard.

Instructions

Read an agent's office inbox (messages from colleagues). Defaults to the caller's own inbox and shows unread items only. Useful for the dashboard or to check what's pending before a run.

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": "kernel_agents_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax messages (default: 20) (max 200)
statusNoFilter by status (default: unread)
agent_idNoAgent whose inbox to read. Defaults to the caller.
__caller_agent_idNo[internal] injected by the agent executor when this tool is invoked from an agent run. Not meant to be set by external callers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does useful work by disclosing the two key defaults (caller's own inbox, unread-only) and implying a read-only operation via 'Read', but it never says whether reading affects message state or interacts with the ack tool, nor does it describe what a message record contains.

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 short sentences with the resource and its defaults front-loaded and the use case last. No filler, though the 'useful for the dashboard' clause is the weakest and least operational part.

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?

A low-complexity, zero-required-parameter read tool with full schema coverage; the description covers scope, defaults, and a usage scenario. The remaining gap is return-value shape, which matters slightly more here because no output schema exists, keeping it from a 5.

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 (limit, status enum, agent_id, injected __caller_agent_id) are already documented structurally. The description restates the same two defaults rather than adding new meaning such as ordering, pagination behavior, or what 'archived' excludes, so baseline 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 specific verb and resource ('Read an agent's office inbox') with a parenthetical clarifying the content ('messages from colleagues'), plus the default scope (caller's own inbox, unread only). It does not distinguish itself from the sibling kernel_agents_inbox_ack, which an agent might reasonably confuse with inbox reading, so it stops short of a 5.

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?

Gives an implied usage context ('useful for the dashboard or to check what's pending before a run'), which is real but soft. There is no statement of when not to use it, and no pointer to kernel_agents_inbox_ack for messages that need acknowledging, leaving the main sibling routing decision to inference.

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