Skip to main content
Glama

kernline_pin

Scrolls a CSS selector into view and pins it in Kernline so the user can see exactly which element was selected.

Instructions

Scroll a selector into view and pin it in Kernline so the user sees what was selected

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "kernline_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoBrowser tab id from kernline_list_tabs; omit when exactly one tab is connected
selectorYesCSS selector to pin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations declare a non-read-only, non-destructive operation, so the description should explain the side effect; it only hints at the viewport scroll. It does not say what 'pinning' actually persists, whether it replaces an existing pin, whether it is idempotent, or what happens if the selector matches nothing.

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 front-loaded sentence with no filler; the action and its user-facing rationale are packed efficiently. There is little room to trim, though the brevity is also part of the ambiguity problem.

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

Completeness2/5

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

For a mutating UI-state tool with no output schema, the definition never explains what a 'pin' is or what the caller gets back, which is the key unknown an agent needs. Full schema coverage offsets some of this, but the core concept remains undefined.

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%, and the schema already documents both the tabId fallback rule and that selector is a CSS selector. The description adds no syntax, matching, or format detail beyond that, so the schema does the work.

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 two concrete verbs (scroll into view, pin) acting on a specific resource (a CSS selector in Kernline), and the trailing clause explains the user-facing effect. An agent can distinguish this from the inspection/capture siblings, though the meaning of 'pin' itself stays opaque.

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 through the purpose clause ('so the user sees what was selected') — i.e. call this when you want the user's viewport focused on an element. There is no explicit when-not guidance and no reference to how this differs from inspect or element_image in a workflow.

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