Catálogo Blucher

Fetch a Blucher book

fetch

Read-onlyIdempotent

Fetch the full record of a Blucher book by the id (ISBN) returned by search: title, authors, edition, price, availability, synopsis and table of contents. / Ficha completa pelo id (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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Book id (ISBN) from search.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	No
`text`	Yes
`title`	Yes
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered elsewhere. The description adds the scope ('full record') versus search's lighter results, but no error behavior (invalid ISBN, not found) or rate/permission context.

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 core sentence is front-loaded with the verb, resource, key input and return fields, with zero filler. The trailing Portuguese sentence is a pure restatement for a reader who already has the English text, a small redundancy.

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 an output schema present, the return values need not be explained, and one parameter plus rich annotations make this a simple tool to call correctly. The only real gap is the unaddressed overlap with the 'obter_livro' sibling.

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 coverage is 100% and the id property is documented as 'Book id (ISBN) from search', so the description only echoes that. No added detail on ISBN format variants or length constraints beyond the schema's min/max.

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 and resource ('Fetch the full record of a Blucher book') plus the exact fields returned, and points to 'search' as the source of the id. It distinguishes itself from search but not from the sibling 'obter_livro', which reads like a synonym for the same operation.

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?

'by the id (ISBN) returned by search' explicitly names the prerequisite step and the input source, which is clear usage context. It stops short of any when-not guidance or of disambiguating against the ambiguous 'obter_livro' sibling.

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?