Skip to main content
Glama

kernline_list_tabs

Read-only

Lists browser tabs where Kernline is open and connected to the local bridge, so you can identify available sources for reading CSS, Tailwind, design tokens, and Copy for AI bundles.

Instructions

List browser tabs where Kernline is open and connected to the local bridge

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add the key behavioral filter (tabs must be open AND connected to the local bridge), which warns that results can be empty when the bridge is down. It does not say what happens when nothing is connected, whether results are cached, or what the local bridge requirement means operationally.

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?

A single front-loaded sentence with no filler; the resource comes first and the scoping constraint follows immediately. Nothing could be removed without losing meaning.

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?

The tool is simple (no params, read-only), but there is no output schema, so the description is the only place an agent could learn the return shape — e.g. whether tabs are identified by id, title, or URL, and whether that identifier is what sibling tools expect. It also omits any mention of the local bridge prerequisite beyond the phrase 'connected to the local bridge'.

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?

There are zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no spurious parameter-like language.

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?

The description gives a specific verb plus resource ('List browser tabs') and adds a meaningful scope qualifier: only tabs where Kernline is open and connected to the local bridge. That separates it conceptually from the sibling tools (inspect, page_summary, asset, pin, etc.), none of which enumerate tabs, though the description does not name any sibling explicitly.

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 only implied: an agent can infer this is a discovery step before acting on a specific tab, but the description states no when-to-use condition, no prerequisite (e.g. bridge must be running), and no exclusion or alternative. It is adequate but leaves routing decisions to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.