Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_unsubscribe_conversation

Cancel a conversation subscription to stop an agent from being woken by new turns; defaults to the caller unless an agent ID is supplied.

Instructions

Cancel a conversation subscription so the agent stops being woken by new turns. Defaults to the caller unless agent_id is supplied.

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_unsubscribe_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoAgent to unsubscribe (defaults to caller)
conversation_idYesConversation to leave
__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

B3.4/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 behavioral burden. It usefully discloses the runtime consequence (no longer woken by new turns) and the default target (caller), but says nothing about idempotency, what happens when the agent was never subscribed, or what the response 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?

Two compact sentences with the effect front-loaded and the targeting rule second; nothing is wasted. The overlap between the second sentence and the schema's agent_id description keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A three-parameter mutation-like operation with no annotations and no output schema needs a bit more: reversibility (can the subscription be restored), error/edge behavior when there is no subscription, and what is returned. The description covers the core intent but not these edges.

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 meaningful parameters are already documented in the schema. The description's second sentence largely restates the agent_id default rather than adding new meaning such as whether an agent can unsubscribe another agent without elevated permissions.

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 ('Cancel a conversation subscription') plus the observable effect ('stops being woken by new turns'), which makes the inverse relationship to subscribe_conversation obvious. It never names the sibling explicitly, so it stops short of the top mark, but an agent can distinguish the two without opening a schema.

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 stated effect (silence wake-ups for a conversation) and by the default-to-caller rule, but there is no explicit when-to-use vs when-not guidance, nor any mention of a list_subscriptions sibling for verifying existing subscriptions first.

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