Skip to main content
Glama

kernline_assets

Read-only

Lists images, SVGs, fonts, and favicons discovered on a page, with an optional tab ID to target a connected browser tab.

Instructions

List page assets discovered by Kernline (images, SVG, fonts, favicons)

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

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.5/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 safe read, so the bar is lower. The description adds real value by defining what counts as an 'asset' (images, SVG, fonts, favicons), but says nothing about whether results are deduplicated, how many are returned, or whether the list is scoped to one tab.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the parenthetical enumeration earns its place by pinning down the asset categories.

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 simple one-parameter read tool with full schema coverage and a readOnlyHint, the safety and input story is complete. However, there is no output schema and the description does not indicate what a returned asset looks like (URL only, typed entries, etc.), leaving the result shape unspecified.

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?

Only one optional parameter and schema coverage is 100%, with the tabId description already explaining the omit-when-one-tab rule. The description adds no additional meaning about tabId, 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?

Specific verb 'List' plus resource 'page assets', with the parenthetical (images, SVG, fonts, favicons) making the scope concrete rather than tautological. It reads clearly as a page-level enumeration tool, though it never explicitly contrasts itself with the singular kernline_asset sibling.

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: 'List page assets' suggests using this when you want an inventory of a page's media. There is no explicit when-to-use versus kernline_asset or kernline_element_image, and no note on prerequisites such as a page needing to be loaded or a tab connected.

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