Skip to main content
Glama

kernline_element_image

Read-only

Capture a PNG screenshot crop of a pinned element or CSS selector from a Kernline-enabled browser tab for visual inspection and sharing.

Instructions

PNG screenshot crop of the pinned element or selector (requires Kernline open on tab)

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating operation. The description adds useful behavior context by stating the output is a PNG crop and that Kernline must be open, but it does not describe how the pinned element and selector interact or what happens when both or neither are supplied.

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?

The description is a single compact sentence with the core output and precondition front-loaded. The parenthetical precondition is efficient, though the sentence could be slightly clearer about the selector-versus-pinned-element relationship.

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 read-only screenshot crop tool with two optional parameters and no output schema, the definition covers the essential output format and runtime precondition. It leaves some ambiguity around selector behavior and the pinned-element fallback, but the tool remains usable from the definition and schema.

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 50%: tabId is documented in the schema, while selector has no schema description. The description implies selector identifies the element to crop, but it does not explain selector syntax, fallback behavior, or what happens when selector is omitted and a pinned element exists.

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 states a specific action and output: a PNG screenshot crop of a pinned element or selector. It distinguishes this from a general screenshot by scoping to an element or selector, but it does not clarify how it differs from sibling capture tools such as kernline_component_capture.

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?

It gives the key precondition that Kernline must be open on the tab, which is useful usage context. However, it does not explain when to use this rather than sibling capture tools, or when to provide a selector versus relying on the pinned element.

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