Skip to main content
Glama
Sign In
zygiu-zygis

basecoat-ui

by zygiu-zygis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_macro_blocks

Read-onlyIdempotent

Find approved macro layout blocks by query, role, family, or tag, and filter by slot-compatible roles for your design page or environment.

Instructions

Search approved macro layout blocks by query, role, family, or tag. Optional design/page/slot context filters to slot-compatible roles. Returns summaries and immutable refs only; use cursors for more.

Input Schema

NameRequiredDescriptionDefault
qNoFull-text search query across macro block IDs, descriptions, and tag sets.
idNoAlternative identifier or query alias.
tagNoSpecific functional tag to filter by (e.g. "sidebar", "data-table", "kpi").
nameNoAlternative identifier or query alias.
roleNoMacro role filter (e.g. "navigation", "canvas", "header", "region", "form").
limitNoMaximum number of block manifests to return per page (1-32, default 10).
cursorNoPagination cursor returned from a previous search.
familyNoBlock family filter (e.g. "layout", "workspace", "auth", "detail").
pageIdNoTarget page ID in the design session when scoping to a slot.
slotIdNoTarget parent slot ID to filter compatible blocks by role.
designIdNoActive design session ID to search with session-specific block registry overrides.
componentIdNoAlternative identifier or query alias.
environmentNoTarget environment.
parentNodeIdNoParent node ID hosting the target slot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.8.0
    • addedInput schema / properties / componentId
      Added value: +{
+  "description": "Alternative identifier or query alias.",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor returned from a previous search."
    • addedInput schema / properties / designId / description
      Added value: +"Active design session ID to search with session-specific block registry overrides."
    • addedInput schema / properties / environment
      Added value: +{
+  "description": "Target environment.",
+  "enum": [
+    "html",
+    "astro",
+    "react",
+    "vue",
+    "svelte"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / family / description
      Added value: +"Block family filter (e.g. \"layout\", \"workspace\", \"auth\", \"detail\")."
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Alternative identifier or query alias.",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of block manifests to return per page (1-32, default 10)."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Alternative identifier or query alias.",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / pageId / description
      Added value: +"Target page ID in the design session when scoping to a slot."
    • addedInput schema / properties / parentNodeId / description
      Added value: +"Parent node ID hosting the target slot."
    • addedInput schema / properties / q / description
      Added value: +"Full-text search query across macro block IDs, descriptions, and tag sets."
    • addedInput schema / properties / role / description
      Added value: +"Macro role filter (e.g. \"navigation\", \"canvas\", \"header\", \"region\", \"form\")."
    • addedInput schema / properties / slotId / description
      Added value: +"Target parent slot ID to filter compatible blocks by role."
    • addedInput schema / properties / tag / description
      Added value: +"Specific functional tag to filter by (e.g. \"sidebar\", \"data-table\", \"kpi\")."
  2. Addedv1.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds meaningful context beyond them: results are 'summaries and immutable refs only' and pagination is cursor-driven. That return-shape disclosure is genuine added value, though rate limits and cursor lifetime are unstated.

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?

Two tight sentences with no filler; the core purpose and the return/pagination caveat are both front-loaded and each clause earns its place.

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 14-parameter, zero-required search tool with no output schema, the description covers purpose, key filters, slot-scoping context, and return shape. It is nearly complete, missing only guidance on choosing among sibling search/list tools and cursor lifecycle.

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 one of the 14 parameters is already documented in the schema. The description echoes the query/role/family/tag dimensions and the design/page/slot context, adding marginal framing but no syntax or precedence detail beyond the schema. Baseline 3 applies.

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?

States a specific verb ('Search') and resource ('approved macro layout blocks') plus the searchable dimensions (query, role, family, tag). An agent can tell it apart from the resource-oriented siblings, though it does not explicitly name search_components or list_blocks as the alternative for a different resource.

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?

The description implies usage by listing filter dimensions and noting that design/page/slot context narrows to slot-compatible roles, but it never states when to prefer this over search_components, list_blocks, or get_macro_block. No exclusions or alternatives are given.

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