Skip to main content
Glama
patrickdeanfox

Zuar Portal Blocks MCP Server

Validate a block (no write)

validate_block
Read-only

Validate block payloads against authoring rules without saving, returning errors and warnings for HTML, JS, CSS to prevent runtime issues.

Instructions

Run the same authoring rules as create_block/update_block against a block payload WITHOUT writing it. Use it to iterate on HTML/JS/CSS until it's clean — it flags the footguns that only surface in a live browser (literal $ String.replace mangling, {{ }} interpolation, data polling, unscoped CSS, full docs, unsafe JS). Returns { valid, errors, warnings }. Pass against_block_id to preview GRANDFATHERING: errors the stored block already has are reported as pre_existing (update_block flags them as warnings instead of blocking).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cssNoCSS section.
dataNoHTML/JS section (the block `data`).
nameNoBlock name (optional for validation).
css_fileNoPath to a file holding the block's CSS; the server reads it into `css`. Same byte-exact guarantee and same root containment as html_file. Mutually exclusive with `css`.
html_fileNoPath to a file holding the block's HTML+JS; the server reads it into json_data.html. PREFER THIS over inlining large content: the bytes are read off disk byte-exact, so nothing is retyped and characters like em dashes or box-drawing cannot silently normalize. Mutually exclusive with json_data.html. Must resolve under the CWD, the VC dir, or a PORTAL_FILE_ROOTS entry.
json_dataNoWidget/extra config.
ui_queriesNoQuery/datasource binding (this is how a block gets data — the portal has no `data` field). Array of { enabled, page_size, query_id, filter_strategy }, e.g. [{ "enabled": true, "page_size": 50, "query_id": "<query-uuid>", "filter_strategy": { "type": "blacklist", "value": [] } }]. The query_id must reference a saved query that already has a datasource attached. On update_block, the existing ui_queries is preserved automatically unless you pass a new value.
against_block_idNoExisting block UUID to compare against — splits errors into new vs pre-existing (grandfathered on update_block).
Behavior5/5

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

The description confirms the readOnlyHint annotation by stating validation without writing. It adds valuable behavioral details such as the return shape {valid, errors, warnings} and the grandfathered error splitting with against_block_id, which go beyond annotations.

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 dense with information in two sentences. It front-loads the purpose and proceeds to list behaviors. While clear, it could be slightly more structured for scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (8 parameters, no output schema, nested objects), the description thoroughly covers the tool's behavior, return format, special cases (grandfathered errors), and references to sibling tools. It is complete and self-contained.

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 each parameter is documented in the schema. The description adds context for against_block_id (grandfathered errors) but does not need to repeat schema details. Baseline score 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?

The description clearly states the tool validates a block using the same rules as create_block/update_block without writing. It lists specific footguns it flags, distinguishing it from its write counterparts.

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?

The description explicitly advises using it to iterate on block payloads during development. It does not explicitly state when not to use, but the context of siblings (create_block, update_block) provides implicit guidance. The grandfathered error mechanism is explained.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/patrickdeanfox/zuar-portal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server