Catálogo Blucher

Ficha completa de um livro

obter_livro

Read-onlyIdempotent

Ficha completa de um livro da Blucher por ISBN (impresso, digital ou de qualquer edição) ou id: autores, edição e se é a vigente, preço em reais, disponibilidade, sinopse, sumário, capítulos, acesso aberto e link de compra. Use para confirmar preço, qual é a edição atual ou se um livro ainda é vendido. Se o ISBN for de uma edição antiga, a ficha diz vigente=false e aponta a atual em edicao.substituido_por. url é o link da página do livro; na edição antiga, edicao.substituido_por.url é o da atual.

Full record of a Blucher book by ISBN (print, digital or any edition) or id: authors, edition and whether it is current, price in BRL, availability, synopsis, table of contents, chapters, open access and purchase link. If the ISBN belongs to an old edition, edicao.substituido_por points to the current one. url is the link to the book's page; for an old edition, edicao.substituido_por.url is the current one's.

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

Input Schema

Name	Required	Description	Default
`id`	No	id do livro devolvido por outra ferramenta. / Book id.
`isbn`	No	ISBN-13 ou ISBN-10, com ou sem hífens; vale o de qualquer formato. / Any ISBN of the book.

Output Schema

Name	Required	Description
`id`	Yes
`url`	No	Página do livro em www.blucher.com.br: o link do livro, o mesmo de `comprar.url`; nula quando o livro saiu do site. / The book's page on www.blucher.com.br (same as `comprar.url`).
`capa`	No
`isbn`	Yes
`selo`	No
`aviso`	No	Limitação desta ficha que o agente deve saber, ex.: `capitulos` cortado nos 60 primeiros (§9.1).
`preco`	Yes
`bisacs`	No
`edicao`	Yes
`titulo`	Yes
`autores`	No
`colecao`	No
`comprar`	Yes
`idiomas`	No
`paginas`	No
`sinopse`	No
`sumario`	No
`formatos`	No
`situacao`	No
`capitulos`	No
`dimensoes`	No
`subtitulo`	No
`acesso_aberto`	Yes
`atualizado_em`	No
`area_principal`	No
`palavras_chave`	No
`disponibilidade`	Yes
`isbns_variantes`	No
`areas_secundarias`	No
`livros_relacionados`	No
`data_disponibilidade`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

addedOutput schema / $defs / EdicaoFicha / properties / substituido_por / description

Added value: +"Em edição antiga (vigente=false): a edição mais recente da obra, com título e link (`url`). / The newer edition of this work, with its title and link."

addedOutput schema / properties / url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Página do livro em www.blucher.com.br: o link do livro, o mesmo de `comprar.url`; nula quando o livro saiu do site. / The book's page on www.blucher.com.br (same as `comprar.url`).",
+  "title": "Url"
+}

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare a safe, read-only, idempotent lookup. The description adds meaningful behavior beyond that: old editions return vigente=false and point to the replacement via edicao.substituido_por, with corresponding URL semantics.

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 first sentence is front-loaded and useful, but the full Portuguese content is repeated in English, effectively doubling length without adding information. The field enumeration is helpful but the bilingual duplication hurts conciseness.

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?

With rich annotations, complete schema descriptions, and an output schema, the description covers the lookup keys, record contents, edition-substitution behavior, and URL meaning. Nothing essential for correct invocation 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%, and both id and isbn are already documented there. The description reinforces that ISBN may be print, digital, or from any edition and that id comes from another tool, but it adds little beyond the schema.

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?

The description states a precise resource ('ficha completa de um livro da Blucher') and the exact lookup keys (ISBN or id), then enumerates the record contents. This is enough to distinguish it from a search/list sibling such as buscar_livros.

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

Usage Guidelines4/5

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

It gives concrete use cases: confirm price, determine the current edition, and check whether a book is still sold. It does not explicitly name alternatives or state when not to use it, but the lookup-by-identifier context is clear.

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

All Catálogo Blucher tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?