Skip to main content
Glama

Read a person's record

get_author
Read-onlyIdempotent

Retrieve a person's Bibliothèque nationale de France authority record by identifier to get birth and death dates, places, occupation, language, country, activity field, and external authority links.

Instructions

Read one person's record in the Bibliothèque nationale de France authority file, by the identifier search_authors returns. It carries the dates and places of birth and death, the occupation the record names, the language and country it associates with the person, the field of activity with its Dewey class, and the addresses for the same person in VIAF, IdRef, DBpedia, Wikidata and ISNI. It carries no biography. The field the BnF calls biographical information is a job title on most records and a single word on many, so quote it as what the catalogue states and do not build a life story out of it. It lists no work. list_works walks from this record to the works the catalogue names the person the creator of, and states what that link does and does not reach. 'depictions' are images data.bnf.fr attaches to the person. They are links for a person to open; this server does not read them, and an image can be a page that mentions the person rather than a portrait of them.

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": {
      "author_id": "<author_id>"
    },
    "name": "get_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
author_idYesThe identifier from search_authors, such as 'cb119219976'. A full data.bnf.fr address is accepted too.
include_depictionsNoInclude the images data.bnf.fr attaches to the person. A well-known person can carry dozens, so they are left out by default. find_digitised gathers them with everything else.

Output Schema

NameRequiredDescriptionDefault
notesYes
authorYes
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. An illustration the record holds elsewhere is not counted, because this server describes Gallica documents and knows nothing about the others.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed32 schema fields changedv2.2.0
    • removedOutput schema / properties / author / properties / biographical_information / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / biographical_information / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / birth_date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / birth_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / birth_place / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / birth_place / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / catalogue_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / catalogue_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / death_date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / death_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / death_place / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / death_place / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / family_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / family_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / given_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / given_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / label / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / label / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / occupation / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / occupation / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / other_names / items / properties / language / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / other_names / items / properties / language / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / record_created / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / record_created / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / author / properties / record_modified / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / author / properties / record_modified / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • 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"
      +]
  2. Changed4 schema fields changedv1.1.0
    • changedOutput schema / properties / author / properties / catalogue_url / description
      Previous value: -"The record in the BnF general catalogue."New 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 a silence in the record rather than a record the general catalogue lacks: no address is built in its place."
    • 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"
      +]
  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?

Annotations already declare read-only/idempotent/open-world, and the description adds substantive context they cannot: the record carries no biography, the 'biographical information' field is often just a job title, depictions are unread external links that may be pages mentioning the person, and works are excluded. This is real guidance about how to interpret what comes back.

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?

Front-loads the verb and resource, then adds caveats in a logical order. It runs long and repeats the caution about the biographical field ('carries no biography' plus the quote-it-as-stated advice), but every clause conveys usable guidance.

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?

With an output schema present the description need not detail return formatting, and it nonetheless covers scope, field inventory, sibling boundaries and interpretation pitfalls. An agent has everything needed to call this correctly and read the result honestly.

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. The description still adds value by saying the id comes from search_authors and by clarifying what 'depictions' actually are (links the server does not read, potentially not portraits), which goes beyond the schema's own wording.

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 and resource ('Read one person's record in the BnF authority file') and enumerates the fields it returns. It explicitly distinguishes itself from search_authors (source of the id), list_works (works are not here) and find_digitised (images).

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?

Ties invocation to search_authors' identifier and routes the agent to list_works for authored works and to find_digitised for images. It does not spell out an explicit 'when not to call this' trigger, but the alternative routing is clear enough.

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