Skip to main content
Glama
brilliant-directories-mcp

brilliant-directories-mcp

Official

getDesignSettings

Read-onlyIdempotent

Read design settings for one or more blocks to retrieve labels, allowed values, and current values; omit the block to list blocks and homepage sections in order.

Instructions

Read design settings by block: labels, allowed and current values. Several blocks in one call: block "hero.primary,hero.cta,home.rows" (up to 30), returned as blocks[]. No arguments: the block list and the homepage sections in order, each Custom Content row with its widget.

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": "getDesignSettings"
  }
}

Input Schema

NameRequiredDescriptionDefault
findNoHomepage text the owner quotes (or a class, id, image, link): returns where it lives. A look the owner describes (ring, circle, glow, box): the CSS properties that draw it (border outline box-shadow border-radius background): returns the homepage elements that set them.
blockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv6.59.638

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is lower. The description still adds real behavior: a batch ceiling of 30 blocks and the exact return structure (blocks[] vs. an ordered block list with Custom Content rows and their widgets).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core purpose, but the phrasing is telegraphic and elliptical ("Several blocks in one call: block \"hero.primary,...\""), which costs parse effort even though few words are wasted.

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?

With two optional parameters, no output schema, and read-only annotations, the definition covers the essential ground: purpose, both parameter paths, batch limits, and return shape. Only explicit routing away from the write sibling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% and the `block` parameter has no schema description, so the description carries that burden — it supplies the concrete format ("hero.primary,hero.cta,home.rows") and the 30-block limit. The `find` parameter's meaning lives in the schema rather than the description, so it is not fully self-contained.

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 opens with a specific verb and resource ("Read design settings by block") plus the fields returned (labels, allowed and current values), which clearly separates it from the sibling updateDesignSettings. It does not name the write sibling explicitly, so differentiation is inferred rather than stated.

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 concrete call-shape guidance: pass a comma-separated block list for multiple blocks in one call (up to 30), or pass no arguments to get the block list and homepage sections in order. What it lacks is an explicit statement of when to prefer this over updateDesignSettings or the other design tools.

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