Skip to main content
Glama

Find a work by its title

search_works
Read-onlyIdempotent

Search the Bibliothèque nationale de France catalogue by title words to find works and retrieve their identifiers and edition lists.

Instructions

Find a work in the Bibliothèque nationale de France catalogue by words in its title, and get the identifier get_work and list_editions take. A row matches when its title carries every word given. The index returns no measure of how well a row matches, so the rows are ordered by the address of the record and the work a person would call the obvious answer can sit anywhere in the list or on a later page. A study of a book carries the book's title, so a search for a famous title returns the criticism alongside the work. Read 'creators' to tell them apart. This reads titles and nothing else. Searching a person's name returns the works written about them, whose creators are their critics; list_works is what walks from a person to the works the catalogue names them the creator of. 'status' says whether the BnF has established the work as a record of its own or holds it provisionally under a title it has catalogued. One search reads a fixed window of the index, and that window is read before the works are told apart from everything else the index holds, so even a short list can rest on a full one. 'index_window_full' says which: when it is true, titles sit past what was read, 'has_more' being false says where the reading stopped, and another reading of the same search can bring back other rows. Add a word to the title to reach further.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
titleYesWords from the title, such as 'saison enfer'. Every word given has to appear.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
notesYes
titleYesThe words asked for.
worksYes
has_moreYesWhether the endpoint held at least one further row beyond this page, within the window the search read off the index. Read it alongside 'index_window_full': false on a full window says where the reading stopped rather than that the catalogue holds nothing else.
retrieved_atYesWhen these metadata were read from data.bnf.fr, as an ISO 8601 instant. The BnF licence asks for this date to be stated wherever the metadata are shown, so repeat it alongside the source.
words_searchedYesThe terms the index required, each of which has to appear in the title. A word is cut at an apostrophe and at a hyphen before the index sees it, so a word given as one can appear here as two, and a record carrying the pieces apart is a match.
index_window_fullYesWhether the fixed window this search reads off the index came back full. The window is read before the works are separated from the rest of the index, so a short list can rest on a full window. True means titles carrying these words sit past what was read, and another reading can bring back other rows. False means the window held everything that matched. Null when the endpoint stated no occupancy.
Behavior5/5

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

Annotations already show readOnly, openWorld, idempotent, and non-destructive. The description goes far beyond this by disclosing that results are not relevance-ranked, are ordered by record address, may include criticism, and that pagination is tied to a fixed index window with 'has_more' and 'index_window_full' flags. This is rich behavioral context that annotations do not capture.

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 detailed and every sentence adds meaningful nuance, but it is somewhat long and dense. It is logically structured and front-loaded with the core purpose, though the later sentences about index windows could be tightened without losing usefulness.

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?

Given the tool's complexity, the description covers ordering, criticism, creator distinction, status, pagination quirks, and differences from sibling tools. The output schema exists, so return values need not be detailed. The description is complete enough for an agent to use the tool correctly and interpret odd results.

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 describes the title parameter well, and the description reinforces it with 'every word given' and 'Add a word to the title to reach further'. However, page and limit parameters are not explicitly explained in the description; their behavior is only indirectly implied through index-window discussion. With low schema coverage (33%), the description should compensate more for these numeric parameters, but it only partially does.

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 clearly states it finds a work by words in its title and returns the identifier used by get_work and list_editions. It also differentiates itself from list_works, which walks from a person to works they created, so it is not merely a generic search description.

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?

It gives explicit guidance on when to use this tool versus alternatives: for title-word searches, and specifically says list_works is the tool for finding works by a person's name. It also instructs reading 'creators' to distinguish criticism from the work itself, which is a clear usage hint.

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/smeet666/mcp-databnf'

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