Skip to main content
Glama

Buscar no Designeer

designeer_search

Search a curated design catalog for inspiration galleries, UI components, libraries, fonts, colors, tools, and designer portfolios. Use it to find references or resources by keyword or collection.

Instructions

Busca no catálogo curado do Designeer (galerias de inspiração, componentes, fontes, cores, ferramentas, portfolios de designers/devs). Use pra achar referência de design, lib de UI, fonte, ferramenta ou portfolio. Retorna nome, tagline, categoria, site e link do Designeer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "designeer_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesTermos de busca em inglês funcionam melhor (ex: 'font', 'motion react', 'landing page gallery')
collectionNoFiltra por coleção

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does usefully disclose the return fields (nome, tagline, categoria, site, link do Designeer), which is valuable given there is no output schema, but it says nothing about ranking/relevance, pagination, rate limits, or whether results are a full or truncated set.

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?

Three short sentences with the core purpose front-loaded and zero filler. The only redundancy is that the usage sentence partly repeats the content-type enumeration from the first sentence.

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 low-complexity, three-parameter search tool with no output schema, the description covers domain, likely intents, and return shape. The remaining gap is result-set behavior (ordering, pagination, limits), which an agent would need before relying on result completeness.

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 coverage is 67%, with query and collection already documented in the schema (including the hint that English terms work better). The description's category list loosely maps to the collection enum but adds no explicit meaning for `limit` or for how `collection` narrows results, so it neither compensates for nor undermines the schema.

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 gives a specific verb+resource ("Busca no catálogo curado do Designeer") and enumerates the catalog contents (galleries, components, fonts, colors, tools, portfolios), so an agent knows exactly what domain is searched. It stops short of distinguishing itself from similar siblings such as designeer_browse or designeer_finds, which is why it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names trigger scenarios ("achar referência de design, lib de UI, fonte, ferramenta ou portfolio"), which implies when to reach for it. However, it offers no when-not conditions and no routing against the other catalog tools (designeer_browse, designeer_finds, designeer_get), so the agent must infer the boundary itself.

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