Skip to main content
Glama
Sign In

NuvUI

by io.github.Nuvraxis
OverviewDiscussionsAdmin

list_blocks

Read-onlyIdempotent

Blocks are screens and parts of apps built from the components, such as a sign-in screen, a dashboard or a pricing table, each a TSX file and an SCSS file to copy and change. Look here before building a screen from nothing.

Input Schema

NameRequiredDescriptionDefault
versionNoThe @nuvui/react version in the project's package.json, such as 0.6.2 or ^0.6.0, for the docs of that release. Leave it out for the latest release.
categoryNoOne of: 3d, accounts, calendar, chat, dashboard, data, editor, flows, layout, marketing, media, settings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"One of: 3d, accounts, chat, dashboard, data, editor, flows, layout, marketing, media, settings."New value: +"One of: 3d, accounts, calendar, chat, dashboard, data, editor, flows, layout, marketing, media, settings."
  2. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"One of: accounts, chat, dashboard, data, editor, flows, layout, marketing, media, settings."New value: +"One of: 3d, accounts, chat, dashboard, data, editor, flows, layout, marketing, media, settings."
  3. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"One of: accounts, chat, dashboard, data, editor, flows, layout, marketing, settings."New value: +"One of: accounts, chat, dashboard, data, editor, flows, layout, marketing, media, settings."
    • addedInput schema / properties / version
      Added value: +{
+  "description": "The @nuvui/react version in the project's package.json, such as 0.6.2 or ^0.6.0, for the docs of that release. Leave it out for the latest release.",
+  "maxLength": 40,
+  "minLength": 1,
+  "pattern": "^(?:\\^|~|>=|=)?v?\\d+(?:\\.(?:\\d+|x|\\*)){0,2}(?:-[0-9A-Za-z.-]+)?$",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"One of: accounts, chat, dashboard, data, editor, layout, marketing, settings."New value: +"One of: accounts, chat, dashboard, data, editor, flows, layout, marketing, settings."
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description usefully adds that blocks are copyable TSX/SCSS assets, but it does not describe result structure, pagination, or filtering behavior.

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 efficient sentences with no filler. The definition is front-loaded enough, though starting with the action ('Lists blocks...') could make the purpose even faster to grasp.

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?

There is no output schema, and the description does not explain what a returned block entry contains beyond being a screen/part with TSX and SCSS files. For a list tool with fully documented optional filters, this is adequate but not complete.

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 version and category are already fully documented in the schema. The description adds no further detail about how filtering by version or category affects the returned blocks, so baseline 3 is appropriate.

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 defines the resource clearly: blocks are screens/app parts built from components, each with a TSX and SCSS file. It does not explicitly say 'lists blocks' or differentiate this listing tool from get_block/list_components, but the examples and file format make the resource recognizable.

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 gives a clear usage cue: 'Look here before building a screen from nothing.' That tells the agent when this discovery tool is appropriate, though it does not name alternatives like get_block or list_components for further inspection.

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

All NuvUI toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources