Skip to main content
Glama

Fetch a HelloBooks public document

fetch
Read-only

Retrieve the full text of one HelloBooks public knowledge document by the id returned from search (e.g. "plan:pro", "deadline:IN:gstr-3b", "competitor:xero"). Returns { id, title, text, url, metadata } where url is the public hellobooks.ai page to cite. Call search first — ids are not guessable.

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

NameRequiredDescriptionDefault
idYesA document id returned by `search`, e.g. "plan:pro" or "deadline:IN:gstr-3b".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish this is a safe read (readOnlyHint=true) against a closed corpus (openWorldHint=false), and the description adds genuinely useful context: it returns full document text plus a citable public `url` and metadata. It does not cover edge behavior such as response size for very long documents or what happens with a stale/unknown id, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the action and followed by the return shape and the precondition. The inline `{ id, title, text, url, metadata }` list partially restates the existing output schema, though the note about `url` being the citation target adds value.

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?

For a one-parameter read tool with 100% schema coverage, an output schema, and safety annotations, nothing needed to call it correctly is missing: the source of the id, its format, and the return contents are all covered.

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%, so the baseline is 3, but the description earns above baseline by stressing that ids are non-guessable and must originate from `search`, plus concrete id shapes ('plan:pro', 'deadline:IN:gstr-3b'). This prevents the agent from fabricating plausible-looking ids.

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?

States a specific verb ('Retrieve the full text') and a specific resource ('one HelloBooks public knowledge document'), and pins scope to a single document keyed by `id`. This clearly distinguishes it from `search`, which finds ids rather than returning document text.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite and routing rule: 'Call `search` first — ids are not guessable.' That tells the agent both when to use the sibling and why this tool cannot be invoked standalone, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources