Skip to main content
Glama

kernline_component_capture

Read-only

Capture a browser tab's component tree as HTML, React, or Vue with Tailwind classes to copy accurate structure for reuse or AI-assisted edits.

Instructions

Pro: component tree capture as html, react, or vue with Tailwind classes

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoBrowser tab id from kernline_list_tabs; omit when exactly one tab is connected
formatNohtml

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a non-mutating capture, and the description is consistent with that. It usefully adds that the captured tree carries Tailwind classes and can be emitted in three frameworks, but it says nothing about output size, multi-component pages, or whether framework output is self-contained. Against an annotation-covered read tool, that is adequate but thin.

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?

A single short sentence that front-loads the resource and the output options with no filler. The only waste is the unexplained 'Pro:' tag, which consumes attention without conveying actionable 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?

For a two-parameter, zero-required read tool with annotations and no output schema, the definition covers the essentials of what it produces. It still leaves the agent unsure how large the result is, whether the tree spans the whole page or a selection, and how framework output should be consumed.

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?

At 50% schema coverage, tabId is fully documented in the schema, and the format enum values (html, react, vue) are restated by the description as emission targets rather than bare strings, which adds a little meaning. However, nothing explains the default or the practical difference between the formats, so it does not fully compensate for the coverage gap. Baseline 3 is appropriate.

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 pairs the specific verb 'capture' with a specific resource, 'component tree', and names the three output formats (html, react, vue) plus the Tailwind-class styling it emits. That is enough to tell it apart from tree-less siblings like kernline_page_summary or kernline_assets, though the differentiation is implied rather than stated. The unexplained 'Pro:' prefix is a small distraction but not a clarity blocker.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all: nothing says to prefer this over kernline_page_summary, kernline_page_tokens, or kernline_inspect, and no prerequisites are given. The only usage cue is the schemas' tabId note pointing at kernline_list_tabs. An agent must infer the selection rule from the sibling names alone.

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