Skip to main content
Glama

View labsUI items

view
Read-only

Read labsUI component or recipe docs by name to get exact props, types, examples, dependencies, and required patterns before writing code.

Instructions

Read the docs of labsUI items by name: exact props and types, a usage line, full examples, and the items and npm packages each brings along; for a recipe, its prompt, the items it uses and the patterns the result needs. Call it before writing code with a component instead of guessing props; find names with search, install with add.

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": {
      "names": "<names>"
    },
    "name": "view"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesItem names as search lists them, e.g. button or date-picker.
sourceNoInclude the source files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / names / description
      Added value: +"Item names as search lists them, e.g. button or date-picker."
  2. First observedv0.1.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally; the description's added value is disclosing what the read returns (props/types, usage line, examples, transitive items and packages, recipe prompts and patterns). It does not mention the batch cap of 10 names or what happens with an unknown name, which keeps it off a 5.

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?

Purpose and payload come first and the routing advice comes last, with no filler sentences. The semicolon-chained clause listing recipe outputs is dense enough to require a second read, which costs it a point but not more.

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?

With no output schema, the description carries the return-value burden and does so concretely for both item types. Minor gaps remain around the 10-name maximum and error behavior, but the schema covers the cap and the tool is a simple read.

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 coverage is 100%, including the name pattern, the 1–10 bound, and the 'source' flag, so the schema already does the parameter work. The description only reinforces 'by name' and never mentions 'source', adding no meaning beyond the structured fields — baseline 3 is appropriate.

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 ('Read the docs of labsUI items by name') and immediately enumerates the payload: props and types, a usage line, examples, bundled items and npm packages. The recipe variant is also named, so an agent knows the tool covers both components and recipes without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit call condition ('Call it before writing code with a component instead of guessing props') and routes the two adjacent steps to siblings: names come from 'search', installation from 'add'. This is a clean when-to-use plus alternatives statement.

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

Deploy Server

Other Tools