Skip to main content
Glama

Áreas, coleções, idiomas e formatos

catalogo_facetas
Read-onlyIdempotent

Lista as áreas, coleções, idiomas e formatos que existem no catálogo da Blucher, com o número de livros de cada. Use antes de filtrar buscar_livros por área, para usar nomes que existem em vez de adivinhar.

Lists the areas, series, languages and formats in Blucher's catalog, with book counts. Use it before filtering buscar_livros by area.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
areasYes
idiomasYes
colecoesYes
formatosYes
atualizado_emNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/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 only that each facet carries a book count and that the catalog is Blucher's; nothing about ordering, empty facets, or stability of names across calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The guidance is front-loaded and the first sentence does the real work, but the entire content is duplicated verbatim in Portuguese and English, roughly doubling length with no new information in the second half.

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 rich annotations, an output schema, and no parameters, the description only needs to convey scope and the reason to call it, which it does. Minor gaps remain around count semantics and whether facet values may be empty.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description doesn't mislead about inputs and correctly implies a parameterless enumeration.

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?

States a specific verb and resource: lists the areas, collections, languages and formats in Blucher's catalog, plus book counts per value. This is clearly distinguishable from buscar_livros, which it explicitly references.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition: use before filtering buscar_livros by area, so you pass real names instead of guessing. Names the sibling and the condition that selects this tool over it.

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