Skip to main content
Glama
Sign In
mcp-brasilapi

mcp-brasilapi

by silasrm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

isbn__buscar

Retrieve book details by entering an ISBN (10 or 13 digits). Provides title, author, publisher, and other bibliographic data from Brazilian sources.

Instructions

Busca informações de um livro a partir do ISBN.

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

Input Schema

NameRequiredDescriptionDefault
isbnYesCódigo ISBN (10 ou 13 dígitos, com ou sem hífens).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the base action. It does not disclose read-only nature, authentication needs, rate limits, or any side effects. The output schema may cover return format, but behavioral traits beyond the action are absent.

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?

The description is a single sentence with no wasted words. While very concise, it could benefit from minor elaboration (e.g., scope of information returned). However, it remains efficient and front-loaded.

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?

Given the tool's simplicity (one required parameter, output schema present), the description is minimally complete. It does not explain return values, but the output schema handles that. The lack of differentiation from sibling tools is mitigated by the unique resource (book info).

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?

The input schema already describes the 'isbn' parameter with format details, achieving 100% coverage. The description adds no additional meaning beyond what is in the schema, so baseline score of 3 is appropriate.

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 'Busca informações de um livro a partir do ISBN' clearly states the verb (search), resource (book information), and input (ISBN). It effectively distinguishes from sibling 'buscar' tools which target different entities like banks or exchange rates.

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 description implies use when an ISBN is available, but no explicit guidance on when to use this tool over alternatives. Sibling names provide context, but the description itself does not specify when to use or exclude other tools.

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

Deploy Server

Other Tools