Skip to main content
Glama

Fiche d'une œuvre

fiche_oeuvre
Read-only

Résumé, créateur, année, note, où la regarder en France et œuvres proches, par identifiant.

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": {
      "id": "<id>"
    },
    "name": "fiche_oeuvre"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, closed-world lookup. The description adds useful scope by saying the record includes French availability and related works, but it does not describe error behavior, missing IDs, or any other operational traits beyond the returned content.

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 a single compact sentence that front-loads the key returned fields and ends with the lookup mechanism. It is efficient, though the phrase 'œuvres proches' slightly blurs the line with the sibling tool of the same name.

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

Completeness3/5

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

For a simple one-parameter lookup with annotations and no output schema, the description adequately lists the main fields returned and the French scope. However, it leaves the identifier source and not-found behavior unspecified, which matters for correct invocation.

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 0%, so the description must carry the parameter meaning. It clarifies that the single integer parameter is an identifier used to fetch the work, but it does not specify what kind of identifier it is, where it comes from, or any format expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool retrieves a work's details by identifier and lists the main fields returned (summary, creator, year, rating, availability in France, related works). It is distinguishable from a search tool because it explicitly works 'par identifiant', though it does not directly name or contrast with the sibling search tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'par identifiant' implies the tool is used when an identifier is already known, but there is no explicit when-to-use guidance, no conditions for choosing this over 'chercher_oeuvre', and no mention of when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources