Skip to main content
Glama
mauricio-cantu

brasil-api-mcp-server

get_isbn

Retrieve book information using an ISBN number. This tool queries BrasilAPI to provide details about books based on their unique identifier.

Instructions

Get information about a book given an ISBN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ISBNYesThe book's ISBN to query

Implementation Reference

  • Executes the tool logic by querying the Brasil API for book details using the provided ISBN and formatting the response.
    handler: async ({ ISBN }): Promise<McpResponse> => {
      try {
        const result = await brasilApiClient.isbn.getBy(ISBN);
        const content: McpTextContent = {
          type: "text",
          text: `Book with ISBN ${ISBN} found:\n${prettifyJson(result.data)}`,
        };
        return {
          content: [content],
        };
      } catch (error: any) {
        console.error(error);
        throw new Error(`Failed to fetch book with ISBN ${ISBN}`);
      }
    },
  • Zod schema defining the input parameters for the get_isbn tool (ISBN string).
    const getISBNToolParams = {
      ISBN: z.string().describe("The book's ISBN to query"),
    };
  • MCP tool definition exporting the get_isbn tool with name, description, params, and inline handler.
    export const getBookByISBNTool: McpToolDefinition<GetISBNToolParams> = {
      name: "get_isbn",
      description: "Get information about a book given an ISBN.",
      params: getISBNToolParams,
      handler: async ({ ISBN }): Promise<McpResponse> => {
        try {
          const result = await brasilApiClient.isbn.getBy(ISBN);
          const content: McpTextContent = {
            type: "text",
            text: `Book with ISBN ${ISBN} found:\n${prettifyJson(result.data)}`,
          };
          return {
            content: [content],
          };
        } catch (error: any) {
          console.error(error);
          throw new Error(`Failed to fetch book with ISBN ${ISBN}`);
        }
      },
    };
  • src/index.ts:30-41 (registration)
    The getBookByISBNTool is included in the tools array and registered to the MCP server using registerTool.
    const tools = [
      getCepTool,
      getCepV2Tool,
      getBookByISBNTool,
      getCNPJTool,
      getAllBanksTool,
      getBankByCodeTool,
    ];
    
    tools.forEach((tool) => {
      registerTool(server, tool);
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic function without details on permissions, rate limits, error handling, or what 'information' includes (e.g., title, author, availability). This leaves significant gaps for an AI agent to understand the tool's behavior beyond the simple query.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool, making it easy for an AI agent to parse quickly.

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 low complexity (1 parameter, no annotations, no output schema), the description is minimally adequate. It covers the basic purpose but lacks details on output format, error cases, or usage context. Without an output schema, the description should ideally hint at what 'information' is returned, but it doesn't, leaving room for improvement.

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 schema description coverage is 100%, with the single parameter 'ISBN' documented as 'The book's ISBN to query.' The description adds no additional meaning beyond this, such as format examples or validation rules. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Get information about a book given an ISBN.' It specifies the verb ('Get information'), resource ('book'), and input ('ISBN'), making the function unambiguous. However, it doesn't differentiate from sibling tools, which are unrelated to books (e.g., get_cnpj, get_postal_code_v1), so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, limitations, or scenarios where other tools might be more appropriate. For example, it doesn't clarify if this is for ISBN-10 or ISBN-13, or if there are other book-related tools available.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mauricio-cantu/brasil-api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server