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

next-ui-mcp

by dylanlindgren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

validate_now_ui_manifest

Validates a now-ui.json manifest against ServiceNow component schema and flags uiBuilder objects missing a non-empty tileIcon path.

Instructions

Validates a now-ui.json manifest using the ServiceNow component-schema-validation package and checks that each uiBuilder object has a non-empty tileIcon path. Accepts either the raw manifest object or a JSON string. Returns whether the manifest is valid and any schema or tileIcon issues found.

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": {
      "manifest": "<manifest>"
    },
    "name": "validate_now_ui_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYesThe now-ui.json object or its raw JSON string to validate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses the validation rules applied (schema package + tileIcon non-empty check), that it accepts either an object or a JSON string, and what the result conveys. It does not state that the operation is side-effect-free, whether it requires instance connectivity, or how validation errors are structured, so it falls short of full disclosure.

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?

Three tight sentences: what it validates, what it accepts, what it returns. Zero filler and the core purpose is front-loaded in the first clause.

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?

For a single-parameter validation tool with no output schema, the description covers the essential gaps by summarizing the return value (validity plus schema/tileIcon issues). It omits error-shape or failure-mode detail, which is minor given the tool's simplicity.

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% for the single 'manifest' parameter and the schema already documents the anyOf object/string acceptance. The description restates that dual input format, adding only marginal value beyond the structured field, so the baseline 3 applies.

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 (validates) and resource (now-ui.json manifest), and names the exact mechanism (ServiceNow component-schema-validation package) plus a second check (non-empty tileIcon on uiBuilder objects). This is clearly distinguishable from the sibling explain_now_ui_manifest, which explains rather than validates.

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?

Usage is implied — you call this when you have a manifest that needs checking before use — but the description never states when to prefer it over explain_now_ui_manifest or what to do with the result. No prerequisites, no when-not conditions, no explicit alternative routing.

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