Skip to main content
Glama

brand_list

Lists curated local brand catalog grouped by category, with optional category filter, to quickly find design references for UI projects.

Instructions

List the curated local brand catalog (62 brands across 7 categories) grouped by category. For DESIGN.md retrieval beyond this list, use brand_fetch_design_md, which resolves the full 328+ brand getdesign catalog.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category filter: productivity-saas|developer-tools|ai-ml|fintech|design-creative|ecommerce|media-consumer|automotive-luxury|legacy-archival

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden. It discloses that the catalog is local and curated (62 brands, 7 categories) versus the remote 328+ catalog, and that output is grouped by category. Auth needs, rate limits, and empty-result behavior for unmatched filters are unstated, which is the only meaningful gap for a read-only listing tool.

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 sentences, both earning their place: the first defines the tool and its scope, the second routes the agent to the sibling for the larger catalog. Front-loaded and free of repetition.

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 one-optional-parameter listing tool with no output schema, the description covers purpose, scope, return grouping, and the alternative tool. Only the behavior when the category filter matches nothing, and the mismatch between '7 categories' and the nine enum values, remain unexplained.

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 the category parameter is already documented, making 3 the baseline. The description adds only the notion of grouping by category and repeats the count '7 categories,' which does not align with the nine enum values in the schema — a small inconsistency an agent may stumble on, though not a contradiction of annotations.

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 (list) and resource (curated local brand catalog) plus scope details: 62 brands across 7 categories, grouped by category. It also explicitly contrasts itself with brand_fetch_design_md, so an agent can distinguish the two without opening either schema.

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?

Provides an explicit routing rule: for DESIGN.md retrieval beyond this list, use brand_fetch_design_md, which serves the larger 328+ getdesign catalog. It does not spell out the inverse condition ('use this tool when browsing or choosing a brand'), but the local-vs-remote split is clear enough to select correctly.

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