Skip to main content
Glama

Buscar produtos

search_products
Read-only

Busca produtos da loja por texto (ex.: "molde de coração", "forma de pirulito") e/ou categoria. Devolve código, nome, preço em reais, disponibilidade, link e imagem de cada produto (um por grupo de variações). Use get_product com o código para ver detalhes e opções.

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

Input Schema

NameRequiredDescriptionDefault
qNoTexto da busca.
paginaNoPágina (20 por página).
categoriaNoSlug de categoria (de list_categories) para filtrar ou listar a categoria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so safety is covered. The description adds useful non-annotation context by describing the response contents and the "one product per variation group" aggregation rule, but says nothing about empty results, ranking, or rate limits.

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 purpose then return shape then the handoff to get_product; no filler. Slightly dense in the enumeration of return fields but every element is informative.

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 no output schema, the description compensates by listing returned fields and the variation-grouping behavior, and pagination is covered in the schema. For a read-only search tool this is close to complete, missing only guidance on zero-result or broad-query behavior.

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 100% (q, pagina, categoria each documented), so the schema carries the parameter burden. The description reinforces meaning with natural-language query examples and the category-slug provenance, but adds no syntax or format detail beyond the schema.

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?

The description names a specific verb and resource ("Busca produtos da loja"), scopes it to text and/or category, and enumerates the returned fields, so the agent can distinguish it from get_product 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?

It explicitly routes detail lookups to get_product with the returned código, and points to list_categories for obtaining a categoria slug. It doesn't state when not to use search (e.g. when a código is already known), so it stops short of full alternative coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources