Skip to main content
Glama

List the works a person is credited with

list_works
Read-onlyIdempotent

Retrieve works linked to an author in the BnF catalogue by identifier from search_authors, returning titles, dates, form codes, record status, and work IDs for editions or digitised documents.

Instructions

List the works the Bibliothèque nationale de France catalogue names one person the creator of, by the identifier search_authors returns. This is the tool for 'what did this person write'. Each row carries the title, the date the record gives the work, the form codes the catalogue points at, whether the record is established or provisional, and the identifier get_work, list_editions and find_digitised take. It is not a bibliography. It reports one link the catalogue holds, and the catalogue credits a person on a record in other ways and holds editions whose work it has never established, so a work missing here is not a work the person did not write. The form codes are the work-form vocabulary's own terms and carry no label in this dataset, so some read as words and some do not. A work stating no code has a form the catalogue does not state, so keeping the rows carrying one code finds the works that declare it and never all the works of that form. Rows are ordered by the address the catalogue gives each work, which is neither chronological nor an order of importance. No total is reported, because the catalogue counts nothing here and a count would read as a measure of what the person wrote.

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": "list_works"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
author_idYesThe person identifier from search_authors, such as 'cb119219976'. A full data.bnf.fr address is accepted too.

Output Schema

NameRequiredDescriptionDefault
pageYes
notesYes
worksYes
has_moreYes
author_idYes
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • removedOutput schema / properties / works / items / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / works / items / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / works / items / properties / title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / works / items / properties / title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Addedv1.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (which only cover read-only/idempotent semantics) by disclosing that rows are ordered by catalogue address rather than chronology, that no total is reported, that form codes are unlabeled vocabulary terms, and that a missing work does not mean the person did not write it. These are exactly the interpreting caveats an agent needs and cannot get from structured fields.

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?

Purpose and scope are front-loaded in the first two sentences, and the caveats that follow each carry distinct meaning. It is long and slightly repetitive in its closing explanation of the absent count, but no sentence is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be re-explained, and the description instead covers provenance, ordering, and vocabulary limitations that the schema cannot express. The remaining gap is that pagination behavior (page/limit semantics, whether more rows exist) is not addressed for a list tool.

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 only 33%: author_id is documented in the schema and reinforced here (from search_authors, example format, full address accepted), but page and limit appear in neither the description nor schema text despite their non-obvious defaults (10) and caps (50). The description compensates partially but leaves the pagination parameters unexplained.

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 scoped to one person ('List the works the BnF catalogue names one person the creator of'), keyed by the identifier search_authors returns. It explicitly frames the intent as 'what did this person write' and distinguishes itself from a bibliography, so an agent can separate it from search_works or get_work.

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?

It names the prerequisite source of the argument (the identifier search_authors returns) and the downstream tools that consume its output (get_work, list_editions, find_digitised), giving clear context for when to call it. It does not, however, explicitly say when to prefer search_works or get_author instead, leaving that comparison to inference.

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