mcp-brasil

Consultar livro por ISBN

consultar_isbn

Read-onlyIdempotent

Retrieves book details including title, authors, publisher, year, and synopsis from an ISBN-10 or ISBN-13. Use it to identify or verify a book from its ISBN.

Instructions

Busca título, autores, editora, ano e sinopse de um livro pelo ISBN-10 ou ISBN-13.

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": {
      "isbn": "<isbn>"
    },
    "name": "consultar_isbn"
  }
}

Input Schema

Name	Required	Description	Default
`isbn`	Yes	ISBN com ou sem hífens

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and external-lookup profile is covered. The description usefully adds that two ISBN formats are accepted and which fields come back, but says nothing about failure behavior (invalid or unknown ISBN), latency, or result completeness.

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 sentence that front-loads the resource and packs the returned fields and accepted formats with zero filler. Nothing is redundant with 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?

For a one-parameter lookup with no output schema, the description covers what the tool does, the accepted input formats, and the shape of the payload. The remaining gap is not-found/error behavior, which an agent would benefit from knowing before relying on it.

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?

Schema coverage is 100% and the schema already documents 'com ou sem hífens'. The description adds genuine extra meaning by specifying that both ISBN-10 and ISBN-13 are valid, which the schema does not state, so it exceeds the baseline 3.

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 ('Busca') and resource ('livro pelo ISBN-10 ou ISBN-13') and enumerates the fields retrieved (título, autores, editora, ano, sinopse). The resource is unambiguously distinct from the sibling lookups (CEP, CNPJ, DDD, taxas), though it never names them explicitly.

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 by the resource: an agent infers it should call this when it has a book ISBN. There is no explicit when/when-not guidance, no mention of alternatives for title/author search, and no note about what to do when the ISBN is not found.

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

Deploy Server