Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_agents_list_subscriptions

List active conversation subscriptions for an agent to prevent duplicate subscriptions and audit which conversations the agent is watching.

Instructions

List active conversation subscriptions for an agent. Useful before subscribing (to avoid duplicates) or to audit what conversations an agent is watching.

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

Input Schema

NameRequiredDescriptionDefault
agent_idNoAgent whose subscriptions to list (defaults to 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.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. 'List' implies a read-only operation and 'active' scopes the result, but nothing is said about pagination, permissions needed to view another agent's subscriptions, or what a returned entry contains.

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 short sentences with zero filler; what it does is front-loaded and the motivating use cases follow immediately.

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 read tool with no output schema, the description covers purpose and motivation adequately. Return shape and result limits are left implicit, which is a minor gap given how lightweight the tool is.

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 coverage is 100%, so agent_id and its 'defaults to caller' behavior are already documented in the schema. The description adds only that subscriptions are filtered by agent, which is marginal beyond the schema itself.

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: 'List active conversation subscriptions for an agent.' That is concrete enough to separate it from sibling list tools such as kernel_agents_list_triggers or kernel_chat_list. It stops short of naming any sibling or contrasting its scope, which keeps it from 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 Guidelines4/5

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

Gives two explicit use cases: avoiding duplicate subscriptions before subscribing, and auditing which conversations an agent watches. It does not list exclusions or name an alternative tool, but the context for calling it is unambiguous.

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