Skip to main content
Glama

Compara MEI: card machines, websites, e-commerce, CRM and ERP for Brazilian small businesses

Buscar maquininha, site, loja virtual, CRM ou sistema de gestão

buscar_produtos
Read-onlyIdempotent

Busca produtos para MEI e pequenas empresas no Brasil por categoria (maquininha, site, loja, crm, gestao), texto livre, uso, só grátis e preço máximo em reais. Para maquininhas devolve também taxas de débito, crédito à vista, Pix e prazo de recebimento.

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

Input Schema

NameRequiredDescriptionDefault
usoNoEx.: mei, comeco, receber_na_hora, sem_aluguel, menor_taxa, gratis, barato, whatsapp, nota_fiscal, estoque, sem_taxa_venda
textoNoEx.: receber na hora, WhatsApp, nota fiscal, dropshipping
gratisNo
limiteNo
categoriaNo
preco_maxNoPreço de entrada máximo em reais

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing that maquininha results include débito, crédito à vista, Pix rates and receival period — output content an agent could not otherwise anticipate, since there is no output schema.

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 dense sentences, front-loaded with the search scope before the maquininha return detail; nothing is padding. Minor redundancy in re-listing the categoria enum values that the schema already declares.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with no output schema and no required parameters, the description covers audience, filter dimensions, and the notable extra fields for maquininhas. The one residual gap, the undocumented 'limite' parameter, is a schema issue rather than something the description was positioned to fix.

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 50%, and the description mostly restates what the schema already says (categoria values, 'só grátis' for gratis, 'preço máximo em reais' for preco_max). The 'limite' parameter has no description in either the schema or the description, so the gap is not compensated.

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?

Uses a specific verb ('Busca') plus resource ('produtos') and enumerates the supported filter dimensions (categoria, texto livre, uso, grátis, preço máximo) with the target audience (MEI e pequenas empresas no Brasil). It does not differentiate itself from siblings like comparar_produtos or melhores_para, so it stops short of 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?

The audience and filter set imply when the tool applies (discovery/search by category or free text), but there is no explicit when-to-use vs when-to-use-another guidance and no sibling is named. Alternatives such as comparar_produtos or ficha_produto are never mentioned, leaving routing to inference.

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