Skip to main content
Glama
Sign In
next-ui-mcp

next-ui-mcp

by dylanlindgren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_instance_components

Search a curated HDS component registry and enrich matches with live ServiceNow instance metadata to help agents discover platform components before choosing dependencies or writing custom UI code.

Instructions

Searches a curated HDS component registry and enriches matches with live ServiceNow instance metadata when available. Use this when an agent needs to discover likely platform components before choosing a dependency or writing custom UI code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_instance_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Defaults to 25.
queryNoFree-text query to match against component tags and known properties/events.
actionNameNoRequire components that dispatch a specific event/action name.
propertyNameNoRequire components that expose a specific property name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results come from a curated registry and are enriched with live instance metadata only 'when available' (i.e., graceful degradation), but it says nothing about ranking, permissions, rate limits, or what happens when no instance connection 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?

Two tightly written sentences with the core behavior front-loaded and no filler. The only mild redundancy is the adjective 'curated', which does not change how the agent invokes it.

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?

No output schema exists, and the description partly compensates by indicating what comes back (registry matches enriched with live instance metadata). All parameters are optional and documented, so an agent has enough to call it; only result ordering/emptiness behavior is unstated.

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 every parameter (query, actionName, propertyName, limit) is already documented in the schema, and the description adds no syntax, matching behavior, or combination semantics beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb ('Searches') and a well-defined resource ('curated HDS component registry'), plus a secondary behavior (enriching matches with live ServiceNow instance metadata). It does not explicitly differentiate itself from close siblings like recommend_instance_components or evaluate_platform_component_fit, but the 'search/lookup' framing is clear.

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?

It states a concrete when-to-use condition: 'when an agent needs to discover likely platform components before choosing a dependency or writing custom UI code.' That is a clear context, but no when-not guidance and no alternative tools (e.g., the recommender or fit-evaluator siblings) are named, so it stops short of full routing guidance.

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