Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_subscribe_conversation

Subscribe an agent to a conversation so each new turn wakes it to read and reply without manual invocation. Set a responder or observer mode and optional role filter.

Instructions

Subscribe an agent to a conversation. Once subscribed, every new turn in that conversation wakes the agent with a run (mode='responder') so it can read and reply without being explicitly invoked. Use this to keep an agent engaged in a thread after invoke/post/meeting hands the topic over. Idempotent — re-subscribing updates the mode/filter. Defaults: subscribe yourself unless agent_id is set.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "kernel_agents_subscribe_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'responder' (default) wakes the agent; 'observer' just records the link
agent_idNoAgent that will follow (defaults to caller)
filter_roleNoOnly wake on this message role (omit = any)
conversation_idYesConversation to follow
__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

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the implicit side effect (each turn spawns a run that wakes the agent), idempotency, and that re-subscribing mutates mode/filter rather than creating duplicates. It is silent on permission requirements and on what the call itself returns, which keeps it below a 5.

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?

Three tight sentences, front-loaded with the action and its effect, then usage context, then defaults. No filler and nothing redundant with the schema.

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 5-parameter mutation tool with no annotations and no output schema, the definition covers effect, usage context, defaults, and idempotency. Remaining gaps are minor: return value of the call and any required privileges.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds real meaning on top: the caller-self default for agent_id and the update-on-resubscribe semantics of mode/filter that the schema does not state. mode and filter_role semantics are already fully described by enum descriptions.

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 ('Subscribe an agent to a conversation') and immediately explains the downstream effect (a run in mode='responder' per new turn), which distinguishes it from unsubscribe/list_subscriptions siblings without naming them.

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 an explicit when-to-use: keep an agent engaged after invoke/post/meeting hands over a topic. It implies but does not state the inverse condition (when not to subscribe, e.g. one-off reads), and never names unsubscribe as the way to stop, so it stops short of full routing guidance.

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