Skip to main content
Glama

kernline_page_tokens

Read-only

Extract design tokens from a browser tab as CSS variables, Tailwind v3/v4, JSON, config, or AI context bundles. Use it to inspect a page's token setup before generating code or theme configs.

Instructions

Pro: scan page design tokens (css variables, tailwind v3/v4, json, or AI context)

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds essentially nothing beyond restating the purpose. It does not say whether the scan is page-wide or element-scoped, whether it requires an active connection/injection, what Pro gating means operationally, or what the returned token payload looks like.

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, front-loaded with the verb and resource, with the format list in parentheses—no wasted words. It is arguably too terse for what it omits, but nothing present is filler.

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?

With only two mostly-optional parameters the surface is small, but there is no output schema, so the description should say what a token scan returns per format—this gap matters given six output modes. The missing explanation of tabId defaults and Pro gating leaves real holes even for a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

tabId is fully documented in the schema, leaving format at 50% coverage; the description's list ("css variables, tailwind v3/v4, json, or AI context") only loosely maps to the enum values css/v3/v4/json/config/tokens. The enum values "config" and "tokens" are never explained, and "AI context" has no obvious enum counterpart, creating ambiguity rather than resolving it.

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?

Uses a specific verb and resource ("scan page design tokens") and enumerates token sources/formats, which tells an agent what it will get back. It does not name a sibling or explain how it differs from captures like kernline_component_capture or kernline_copy_for_ai, so it stops short of full differentiation.

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 guidance, no preconditions, and no mention of when another sibling (e.g., an inspect or copy-for-AI tool) would be the better choice. The only implicit cue is the "Pro:" prefix, which hints at a plan restriction but never states it.

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