Skip to main content
Glama

Add a custom live component to the Lab

inspo_add_component

Add a custom live component demo to the board's Lab for user voting alongside the built-in library. Submit one standalone HTML document tinted with the board's CSS variables.

Instructions

Add your own live component demo (3D hero, shader, scroll effect, micro-interaction...) to the board's Lab so the user can vote on it next to the built-in library. Must be one standalone HTML document. Use CSS vars --bg --fg --muted --accent --accent2 so the board can re-tint it with a liked style; libraries only from CDN (three via importmap from cdn.jsdelivr.net).

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": {
      "name": "<name>",
      "category": "<category>",
      "description": "<description>",
      "html": "<html>"
    },
    "name": "inspo_add_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYes
nameYes
tagsNo
sessionNoSession id. Defaults to the most recent session in this project.
categoryYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the hard content contract (single standalone HTML document), the theming contract (--bg/--fg/--muted/--accent/--accent2 CSS vars so the board can re-tint), and the dependency constraint (CDN libraries only, three via importmap from cdn.jsdelivr.net). It says nothing about what happens on success — whether an id is returned, whether the component is immediately votable, or what happens on validation failure.

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?

Three dense sentences, front-loaded with the action and the voting rationale, then the content constraints. No filler, though the CSS-variable enumeration is a bare list that assumes the reader knows it is a requirement rather than an example.

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 write tool with no annotations and no output schema, the description covers content constraints well but leaves the return contract and validation behaviour unexplained. An agent knows what to put in but not what it gets back or how failures surface, which is a meaningful gap for a creation tool.

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 17% across 6 parameters, so the description must compensate and it only partially does. It adds real meaning for html (standalone document, must expose theming vars, CDN-only deps), which the schema describes only as a string with minLength 50. It says nothing about name, description, tags, session, or which category values exist, leaving five of six parameters to the raw schema.

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 a specific verb and resource: add a user-supplied live component demo to the board's Lab for side-by-side voting with the built-in library. The parenthetical examples (3D hero, shader, scroll effect, micro-interaction) pin down what counts as a component, which separates it from sibling adders like inspo_add_images or inspo_add_styles without naming them.

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?

Implies the when: the agent should use this to contribute a custom demo the user will vote on. It never states when NOT to use it (e.g. versus inspo_add_build, the likely alternative for generated builds) or that the component must supplement, not replace, the built-in library. Usage is inferable but not explicit.

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