Skip to main content
Glama

Escudo Compara: VPN, password managers and antivirus (Brazil and Latin America)

Categorias e usos

categorias
Read-onlyIdempotent

Lista as categorias, os ids dos produtos de cada uma, os usos aceitos e a data da última conferência de preços.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing what is actually returned — per-category product ids, accepted uses, and the timestamp of the last price check — which matters because no output schema exists. It omits ordering, volume, or staleness caveats, keeping it at 4.

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?

A single front-loaded sentence: verb and resource first, then the returned fields. Every clause maps to a distinct piece of returned data and there is no filler or repetition of annotations.

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?

For a zero-argument, read-only listing tool with full annotation coverage, the description is nearly sufficient: it tells the agent what data comes back despite the absence of an output schema. Minor gaps remain around result ordering/shape (e.g., whether 'usos' is per category or global) and whether the data can be stale.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The schema coverage is 100% with an empty object, consistent with the description.

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 opens with a specific verb+resource ('Lista as categorias') and then enumerates the payload: category names, product ids per category, accepted uses, and the last price-check date. An agent knows exactly what this tool returns. It does not explicitly contrast itself with siblings like buscar_produtos or ficha_produto, which keeps it below 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?

Usage is only implied: as a zero-parameter listing tool it reads as a discovery/entry point for the category taxonomy, but the description never says when to call it versus the sibling search tools. No exclusions or prerequisites are stated.

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