Skip to main content
Glama

Navegar uma coleção

designeer_browse

Browse collections of design inspiration, resources, tools, or portfolios in their curated order with pagination and optional category filters to find relevant assets quickly.

Instructions

Lista os itens de uma coleção do Designeer na ordem curada, com paginação. Categorias conhecidas: tools-development, tools-capture-media, tools-design-canvas, resources-type-color, resources-components, inspiration-galleries (há outras; os itens trazem category_slug).

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": {
      "collection": "<collection>"
    },
    "name": "designeer_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor da página anterior
categoryNoSlug de categoria, ex: 'tools-design-canvas'
collectionYes

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?

With no annotations at all, the description carries the full behavioral burden and does disclose meaningful traits: results come back in curated order, pagination is supported, and items expose a category_slug field. It stops short of stating that this is read-only, how large pages are, or what happens with an invalid or exhausted cursor.

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 sentences, front-loaded with the action and its scope before the taxonomy support detail. The category enumeration is long but earns its place as discovery aid; the parenthetical about other categories prevents it from being read as a closed set.

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?

With no output schema and no annotations, the description must cover both safety profile and return shape; it partially does by naming the category_slug item field and the pagination model. Gaps remain around page size, ordering rules across collections, and the fact that this is a non-mutating read.

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 67%, so the schema already documents cursor and collection. The description adds genuine value for `category` by enumerating known slugs that appear nowhere in the schema (which only offers a single example) and by warning that the list is non-exhaustive and discoverable through category_slug on returned items.

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 and resource ("Lista os itens de uma coleção") plus the ordering guarantee ("na ordem curada") and pagination. It is clearly distinguishable from mutation siblings like designeer_capture or designeer_component, though it never names the read-side alternatives (designeer_finds, designeer_search, designeer_get) it could be confused with.

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?

Usage is only implied: the category taxonomy makes clear this is a browse-within-a-collection tool, but the description never states when to choose it over designeer_search or designeer_finds, nor any precondition. The category list is helpful orientation rather than a selection rule.

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