Skip to main content
Glama
smeet666

mcp-databnf

by smeet666
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Read a work's record

get_work
Read-onlyIdempotent

Retrieve a work's catalogue record from the Bibliothèque nationale de France by its identifier, with title, credits, date, language, form, subject, Dewey class, and status.

Instructions

Read one work's record in the Bibliothèque nationale de France catalogue, by the identifier search_works returns. It carries the title, everyone the record credits, the date the BnF gives the work, its language, its form and its subject with the Dewey class. 'forms' holds the work-form vocabulary's own terms, which carry no label in this dataset, so some read as words and some do not. A record stating none has a form the catalogue does not state. 'status' says whether the record is established or provisional, and 'status_statement' repeats what the catalogue itself states. A provisional identifier can change, so cite an established one where there is a choice. 'expression_count' counts the expressions the record links, which is not a count of published editions: use list_editions for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
work_idYesThe identifier from search_works, such as 'cb11970626n' or 'temp-work/22d7f68c1a4bdd081ad7ca791fd3b730'.
include_depictionsNoInclude the images data.bnf.fr attaches to the work. A well-known work can carry dozens, so they are left out by default. find_digitised gathers them alongside the digitised editions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
workYes
notesYes
depictionsNo
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.
depiction_countYesImages on Gallica that the record points at, counted whether or not they were returned.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv1.1.0
    • addedOutput schema / properties / depictions / items / properties / rendering
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The view the address asks Gallica for, read off what follows the ARK name in it, such as 'thumbnail' for a small image or 'item' for one leaf. Null when the address names the document itself. This says what was asked for, not what comes back."
+}
    • changedOutput schema / properties / depictions / items / properties / url / description
      Previous value: -"Open this to see the document. This server does not read it."New value: +"The address the catalogue publishes, for a person to open. Read it beside 'rendering': an address asking for a rendering opens that view of the document rather than the document. This server does not read either."
    • changedOutput schema / properties / depictions / items / required
      Previous value: -[
-  "ark",
-  "url",
-  "role",
-  "from_id",
-  "from_title"
-]New value: +[
+  "ark",
+  "url",
+  "rendering",
+  "role",
+  "from_id",
+  "from_title"
+]
    • addedOutput schema / properties / work / properties / catalogue_url / description
      Added value: +"The address of this record in the BnF general catalogue, as the record itself points at it. Null when the record states none, which is the ordinary case on work records: it is a silence in the record rather than a record the general catalogue lacks, and no address is built in its place."
    • changedOutput schema / properties / work / properties / forms / description
      Previous value: -"Forms from the BnF work-form vocabulary, such as 'poesi' for poetry."New value: +"Terms of the BnF work-form vocabulary, as the terms themselves. The vocabulary publishes no label for them here, so they are not translated: some read as words, such as 'poesi', and some do not, such as 'te'. An empty list is a form the record does not state."
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

The description goes beyond the readOnlyHint annotation by clarifying nuances: forms use a vocabulary with no labels, status indicates provisional vs established, and expression_count does not equal edition count. It also explains the default behavior of include_depictions (left out due to large payloads) and points to find_digitised for images alongside digitised editions.

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 dense but every sentence contributes either to scope, field semantics, or usage caveats. Some phrasing, like 'A record stating none has a form the catalogue does not state,' is awkward but not confusing. It is front-loaded with the purpose and then details.

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 rich schema and output schema, the description provides enough context for an agent to understand the tool's purpose, its data semantics, and its relationship to sibling tools. It covers the main caveats (provisional IDs, form labels, edition count distinction) and is self-contained.

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?

The schema already provides descriptions for both parameters (100% coverage). The description reinforces the identifier's origin from search_works and adds guidance about preferring established identifiers, which supplements the schema's example. It does not discuss include_depictions separately since the schema covers it well.

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 the tool's purpose: 'Read one work's record in the Bibliothèque nationale de France catalogue, by the identifier search_works returns.' It specifies the verb (read), resource (work's record), and source (BnF). It also distinguishes from siblings by explicitly directing users to list_editions for edition counts.

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?

The description explains that the identifier comes from search_works, implying a search-then-read workflow. It also warns that provisional identifiers are changeable and recommends citing established ones, and explicitly says to use list_editions for published edition counts instead of this tool.

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