Skip to main content
Glama

show_card

Display a draggable floating card with self-contained HTML, such as a diagram, animation, or interactive demo, directly on the current browser page.

Instructions

Show a floating card on the page containing HTML you write: a diagram, an animation, a worked example, a small interactive demo. The HTML must be self-contained (inline , , SVG or canvas); it runs isolated with no network access, so no external scripts, fonts, images or fetch (data: images are fine). Design it for the given size without scrolling, and support light and dark with prefers-color-scheme. The user can drag and close the card. A new card replaces the ones you showed before unless keep is true. The result says whether the content actually drew; if it reports an error or an empty body, fix the HTML rather than telling the user it is there.

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": {
      "tabId": "<tabId>",
      "html": "<html>"
    },
    "name": "show_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoPlace the card beside this element; default is the bottom-right corner
htmlYesA complete HTML document, or body content
keepNoLeave your earlier cards on the page (default: replace them)
tabIdYesTab ID, from tabs_list or tab_create
titleNoShown in the card header
widthNoPixels, default 400
heightNoPixels, default 300

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: isolation with no network access, the self-contained HTML constraint with concrete examples of what is forbidden (external scripts, fonts, images, fetch), no-scroll sizing, light/dark support via prefers-color-scheme, user drag/close, and replacement semantics. It even discloses the return signal ("whether the content actually drew") and instructs how to react to failure.

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?

One dense paragraph, front-loaded with the action and payload, then constraints, then lifecycle, then error handling. Every sentence adds operational information; nothing is padding.

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

Completeness5/5

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

Although there is no output schema, the description still explains what the result reports and what to do when it reports failure. All 7 parameters are either covered by the schema or given behavioral context, so nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning on top by explaining that a new card replaces prior cards unless keep is true and that width/height must be designed for without scrolling. The ref and title parameters are left entirely to their schema descriptions.

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?

States a specific verb and resource ("Show a floating card on the page containing HTML you write") and enumerates concrete payload types (diagram, animation, worked example, interactive demo). It is clearly distinct from siblings like close_cards, screenshot, and javascript.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this is the right tool (rendering visual HTML content for the user) and describes the replace-by-default versus keep=true condition. It stops short of naming explicit alternatives such as screenshot or javascript for cases where this tool is not appropriate.

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