Skip to main content
Glama

create_uib_component

Create a custom UI Builder component (macroponent) by specifying name, label, category, and description.

Instructions

Create a custom UI Builder component (macroponent). [Scripting]

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>",
      "label": "<label>"
    },
    "name": "create_uib_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesComponent name
labelYesDisplay label (macroponents have no label field, so it is used as the description when none is given)
categoryNoComponent category (e.g. component, page, primitives)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • changedInput schema / properties / category / description
      Previous value: -"Component category"New value: +"Component category (e.g. component, page, primitives)"
    • changedInput schema / properties / label / description
      Previous value: -"Display label"New value: +"Display label (macroponents have no label field, so it is used as the description when none is given)"
  2. First observedv1.0.2

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds only that the target is a 'macroponent' and tags it as scripting; it does not explain duplicate handling, permission needs, or what happens when a component with the same name exists.

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?

The description is very short and front-loaded with the action and resource. The trailing '**[Scripting]**' tag is terse and somewhat cryptic, but there is no wasted prose.

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 creation tool whose annotations and input schema carry safety and parameter information, the description is minimally adequate. However, it omits usage context, duplicate-name behavior, and parameter nuances that would help an agent invoke it correctly.

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

Parameters2/5

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

Schema description coverage is 75%, with category lacking examples and the description parameter lacking schema text. The description does not clarify parameter meaning, category values, or the special label/description behavior documented in the 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?

The description clearly states a specific verb and resource: 'Create a custom UI Builder component (macroponent).' It distinguishes the created artifact from sibling resources like pages and data brokers, but does not explicitly contrast with create_uib_page or create_uib_data_broker.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The description only implies that this is the creation tool for UI Builder components.

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