Skip to main content
Glama

Chercher une œuvre

chercher_oeuvre
Read-only

Cherche un film, une série, un livre, un jeu vidéo, un album, un animé ou une œuvre d'art dans le catalogue RaryLib, par titre ou créateur.

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": {
      "texte": "<texte>"
    },
    "name": "chercher_oeuvre"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoUnivers à filtrer.
texteYesTitre ou nom du créateur.
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description usefully reinforces the closed, internal nature of the search ('catalogue RaryLib'). It adds nothing about the default result cap of 6, the maximum of 15, or what a result entry contains, so it goes beyond annotations only modestly.

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?

One front-loaded sentence naming the action, the catalogue, the covered media types and the search axis, with no filler. The media enumeration is long but functional since it defines the tool's scope.

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?

For a three-parameter, non-destructive search with no output schema and no nesting, the definition covers scope, catalogue and search fields adequately. The gaps (result limit semantics, behaviour without a 'type' filter, result shape) are minor but real.

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 coverage is 67%: 'type' has an enum with its own description and 'texte' is documented in the schema; the description's 'par titre ou créateur' restates rather than extends that meaning. The 'limite' parameter is undocumented in both schema and description, and the description does not clarify behaviour when 'type' is omitted.

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 gives a specific verb ('Cherche') plus the resource (œuvre within the RaryLib catalogue), enumerates the media universes covered, and states the search axes ('par titre ou créateur'). It does not distinguish itself from siblings like fiche_oeuvre or oeuvres_proches, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: 'dans le catalogue RaryLib, par titre ou créateur' tells the agent this is a lookup-by-name entry point, but there is no explicit statement of when to prefer it over fiche_oeuvre or oeuvres_proches, nor any exclusion or prerequisite.

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