Skip to main content
Glama

Que lire ou voir après

oeuvres_proches
Read-only

Les œuvres liées à une œuvre : même univers, suites, adaptations, même auteur.

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

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds real value by telling the agent what kind of results come back (related works by relation type), but says nothing about ordering, completeness, or whether the list can be empty.

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?

A single short sentence, front-loaded with the core action and followed by the relation categories. No filler, though the phrasing 'Les œuvres liées à une œuvre' is slightly circular.

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?

There is no output schema, so the description should carry the return-value burden; it partially does by naming the relation types, but leaves the sole input undefined and gives no hint about result shape or volume. Adequate for a simple read tool, but with a clear gap on the parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 0% schema description coverage, the description must explain what `id` is, and it does not — it never says the id refers to a source work whose relations are returned. The agent has to infer that from the tool name and title alone.

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?

States a specific operation: retrieving works related to a given work, and enumerates the relation types (same universe, sequels, adaptations, same author). This clearly separates it from fiche_oeuvre (detail) and chercher_oeuvre (search), though it never names a sibling explicitly.

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?

The title 'Que lire ou voir après' implies a recommendation/discovery use case, and the description reinforces it by listing the kinds of relations. There is no explicit when-to-use versus fiche_oeuvre or chercher_oeuvre guidance, and no stated preconditions (e.g. that the id must reference an existing work).

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