Skip to main content
Glama

Read a work's record

get_work
Read-onlyIdempotent

Retrieve a specific work's Bibliothèque nationale de France catalogue record by its search_works identifier to inspect title, creators, date, language, form, subject, 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.

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": {
      "work_id": "<work_id>"
    },
    "name": "get_work"
  }
}

Input 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

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.

  1. Changed16 schema fields changedv2.2.0
    • removedOutput schema / properties / depictions / items / properties / from_title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / depictions / items / properties / from_title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / depictions / items / properties / rendering / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / depictions / items / properties / rendering / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / work / properties / catalogue_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / work / properties / catalogue_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / work / properties / creators / items / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / work / properties / creators / items / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / work / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / work / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / work / properties / label / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / work / properties / label / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / work / properties / status_statement / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / work / properties / status_statement / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / work / properties / title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / work / properties / title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. 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."
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavioral and data-quality traits: forms come from a vocabulary without labels, an unstated form means the catalogue does not state one, provisional identifiers can change, and expression_count is not an edition count. These are substantive operational caveats that help an agent interpret the result correctly.

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 front-loaded with the core purpose and then moves through the most important field semantics in one dense paragraph. It is longer than a minimal definition but every sentence conveys relevant caveats; it could be slightly easier to scan with structure, but there is little wasted text.

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 that an output schema exists, the description does not need to enumerate return values, and it instead supplies the semantic caveats an agent needs: field meanings, vocabulary limitations, status behavior, and the expression_count distinction. It is complete for calling and interpreting this read tool correctly.

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 description coverage is 100%, and the schema already documents both work_id and include_depictions, including the identifier source and the default exclusion of images. The description reinforces that work_id comes from search_works but adds little parameter-level detail beyond what the schema already provides, so the high-coverage baseline of 3 applies.

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 states a specific verb and resource: read one work's record in the BnF catalogue, by an identifier returned from search_works. It distinguishes itself from siblings by naming search_works as the identifier source and list_editions as the tool for published editions, so an agent can place it without opening another schema.

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 routing: use this when you have an identifier from search_works; use list_editions for published editions; and cite an established identifier rather than a provisional one when there is a choice. These are clear when-to-use conditions and alternative-tool instructions rather than implied guidance.

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