scrypta-mcp-server

Buscar Produtos

buscar_produtos

Read-onlyIdempotent

Busca produtos no catálogo. Aceita filtros combinados: termo no nome, categoria, faixa de preço e apenas em estoque. Retorna lista paginada com nomes, preços e URLs.

Input Schema

Name	Required	Description
`query`	No	Termo de busca por nome do produto (ex: 'colar', 'vestido'). Aceita acentos ou não.
`limite`	No	Número máximo de produtos por resposta (1 a 100). Default: 20.
`offset`	No	Quantos resultados pular (paginação). Default: 0.
`categoria`	No	Nome exato da categoria (ex: 'Colares'). Use listar_categorias antes para descobrir nomes válidos.
`preco_max`	No	Preço máximo em BRL (inclusivo). Ex: 100.00 para até R$ 100.
`preco_min`	No	Preço mínimo em BRL (inclusivo). Ex: 50.00 para a partir de R$ 50.
`apenas_em_estoque`	No	Se true, retorna apenas produtos em estoque. Default: false.

Output Schema

Name	Required	Description
`total`	Yes	Total de produtos que casam com os filtros.
`has_more`	Yes	True se há mais páginas.
`products`	Yes
`returned`	Yes	Quantos vieram nesta página.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 31, 2026

addedInput schema / properties / apenas_em_estoque

Added value: +{
+  "description": "Se true, retorna apenas produtos em estoque. Default: false.",
+  "type": "boolean"
+}

addedInput schema / properties / categoria

Added value: +{
+  "description": "Nome exato da categoria (ex: 'Colares'). Use listar_categorias antes para descobrir nomes válidos.",
+  "type": "string"
+}

addedInput schema / properties / limite

Added value: +{
+  "description": "Número máximo de produtos por resposta (1 a 100). Default: 20.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Quantos resultados pular (paginação). Default: 0.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / preco_max

Added value: +{
+  "description": "Preço máximo em BRL (inclusivo). Ex: 100.00 para até R$ 100.",
+  "type": "number"
+}

addedInput schema / properties / preco_min

Added value: +{
+  "description": "Preço mínimo em BRL (inclusivo). Ex: 50.00 para a partir de R$ 50.",
+  "type": "number"
+}

addedInput schema / properties / query / description

Added value: +"Termo de busca por nome do produto (ex: 'colar', 'vestido'). Aceita acentos ou não."

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "has_more": {
+      "description": "True se há mais páginas.",
+      "type": "boolean"
+    },
+    "products": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "in_stock": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Quantos vieram nesta página.",
+      "type": "integer"
+    },
+    "total": {
+      "description": "Total de produtos que casam com os filtros.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "products",
+    "total",
+    "returned",
+    "has_more"
+  ],
+  "type": "object"
+}

First observedOct 16, 2026

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, closed-world behavior, so the safety profile is covered. The description adds useful context beyond them by noting that results are paginated and what fields come back (nomes, preços, URLs), though it omits any note on default page size or empty-result behavior (the latter is covered by the schema).

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 short sentences: the first states the action, the second states filters and return shape. Front-loaded and free of filler, with nothing repeated from the title.

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 seven optional parameters, full schema coverage, annotations, and an output schema, the definition supplies what is needed to call it correctly. It is slightly thin on routing to siblings and on pagination defaults, but nothing critical is missing.

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 baseline is 3. The description restates four of the seven parameters (name term, category, price range, in-stock) but adds no syntax or format detail beyond the schema, and never mentions limit/offset pagination controls.

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?

States a specific verb and resource ("Busca produtos no catálogo") and enumerates the filter facets it accepts, so the agent knows exactly what the tool does. It does not name or contrast with siblings like produtos_por_categoria or listar_categorias, so differentiation is left implicit.

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 phrase "Aceita filtros combinados" implies this is the general-purpose filtered search, but there is no explicit when-to-use or when-not guidance versus produtos_por_categoria (already-filtered listing) or listar_categorias. Usage must be inferred from the parameter list rather than stated.

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

All scrypta-mcp-server tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.