Skip to main content
Glama

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

Melhores para um uso

melhores_para
Read-onlyIdempotent

Lista os produtos de uma categoria indicados para um uso (ex.: maquininha para receber na hora, loja virtual sem taxa por venda, sistema para emitir nota), do menor para o maior preço.

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": {
      "categoria": "<categoria>"
    },
    "name": "melhores_para"
  }
}

Input Schema

NameRequiredDescriptionDefault
usoNo
limiteNo
categoriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact beyond that — results are sorted ascending by price — but says nothing about what happens when the optional 'uso' is omitted or how results are capped.

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?

One well-formed sentence that front-loads the action and closes with the ordering rule. The triple parenthetical is slightly dense but each example clarifies a distinct use case, so it largely earns its space.

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 zero schema description coverage, the description does enough to convey purpose, sort order, and use-case examples, but the undocumented 'limite' parameter and the absent behavior when 'uso' is missing leave real gaps for an agent to guess at.

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 0%, so the description must carry the parameter burden. It explains 'categoria' (products of a category) and gives rich examples of 'uso', but never mentions 'limite' at all, leaving one of three parameters completely undefined in both schema and prose.

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: it lists products within a category that are suited to a given use case, and it specifies the ordering (lowest to highest price). This distinguishes it reasonably well from generic product search or comparison siblings, though it never names an alternative.

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 parenthetical examples (maquininha para receber na hora, loja virtual sem taxa por venda, sistema para emitir nota) give concrete context for what a 'uso' looks like, which implicitly guides usage. However, there is no explicit statement of when to choose this over buscar_produtos, alternativas, or kit_para_negocio, and no exclusions.

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