Skip to main content
Glama

kernline_copy_for_ai

Read-only

Copies HTML, computed CSS, design tokens, sizes, and states for the pinned element into an AI-ready bundle, so MCP clients can inspect and reuse exact UI styling.

Instructions

Pro: copy-for-AI bundle (HTML, computed CSS, tokens, sizes, states) for the pinned element

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

Input Schema

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

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?

Annotations already declare readOnlyHint=true, so the safety profile is partly covered, and the description adds useful scope detail about what the bundle contains. It does not say whether the result is returned as text/JSON or placed on the clipboard (the name 'copy' suggests a clipboard side effect worth clarifying against readOnlyHint), nor what happens if no element is pinned or how the 'Pro' gating affects behavior.

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 tight sentence that front-loads the artifact and then enumerates its components; every clause carries information. It is dense but not padded.

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

Completeness5/5

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

Placeholder.

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?

With one optional parameter and 100% schema description coverage, the schema already explains that tabId comes from kernline_list_tabs and may be omitted with a single connected tab. The description adds no meaning about the parameter, so the baseline 3 applies.

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 names the concrete artifact ('copy-for-AI bundle') and enumerates its contents (HTML, computed CSS, tokens, sizes, states) scoped to 'the pinned element', which is specific enough to separate it from image/capture siblings. It stops short of naming which sibling it supersedes, so it is clear but not fully differentiated.

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?

'for the pinned element' implies a prerequisite (the element must already be pinned via kernline_pin) and implies usage context, but the definition never states when to prefer this over kernline_component_capture, kernline_inspect, or kernline_element_image, all of which could plausibly produce similar output. Usage is inferable rather than stated.

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