Skip to main content
Glama

kernline_asset

Read-only

Fetches a single asset by ID and returns it as inline SVG or text, capped by size, for use in MCP clients.

Instructions

Fetch one asset by id from kernline_assets (inline SVG or text, size-capped)

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": {
      "id": "<id>"
    },
    "name": "kernline_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAsset id from kernline_assets
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

A4/5.0
Behavior4/5

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

The readOnlyHint already establishes that this is a safe read operation. The description adds useful behavioral detail beyond annotations by noting that the result is inline SVG or text and that output is size-capped, though the exact cap and error behavior remain unspecified.

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?

The definition is a single front-loaded sentence with no wasted wording. The parenthetical efficiently adds return-format and size-cap context.

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 fetch tool with full schema descriptions and a readOnly annotation, the description is nearly complete. It covers the resource, id source, and payload type despite having no output schema, with only exact cap and error handling absent.

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 description coverage is 100%, so the schema already explains both id and tabId. The description reinforces that id comes from kernline_assets but adds no meaning for tabId or any constraint beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Fetch one asset by id from kernline_assets." The singular asset scope distinguishes it from the plural kernline_assets list tool, and the parenthetical clarifies the returned formats.

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?

The description implies retrieval when an id is known and references kernline_assets as the source of ids, but it does not explicitly say when to use this tool versus listing or inspecting alternatives. No when-not guidance or prerequisite workflow is stated.

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