Skip to main content
Glama

Où regarder en France

ou_regarder
Read-only

Plateformes d'abonnement qui proposent ce film, cette série ou cet animé en France.

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

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 the safety profile is covered. The description adds a useful behavioral constraint beyond that - results are limited to subscription platforms and to France - but says nothing about coverage gaps (e.g. whether an empty list means unavailable or unknown) or about the id's origin.

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 with no filler; the resource being returned leads and the geographic scope follows. It is arguably too terse for the ambiguity it leaves, but nothing is wasted.

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 read-only lookup this is close to adequate, and annotations carry the safety profile. However, with no output schema and no parameter descriptions, the definition should at least clarify what the id is and what kind of platform entries come back (names, links, availability).

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?

Schema description coverage is 0%, so the single 'id' parameter is undocumented in structured data and the description must compensate. It only indirectly implies the id identifies a work ('ce film, cette série ou cet animé') without saying which identifier namespace or format is expected, leaving a real ambiguity for a one-parameter tool.

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 names the resource precisely (subscription platforms offering a movie, series or anime) and scopes it geographically to France, so an agent can tell it apart from siblings like fiche_oeuvre or oeuvres_proches. The verb is implicit in 'qui proposent' rather than stated as a lookup action, which keeps it 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: the phrase 'plateformes d'abonnement' implicitly excludes rental/purchase lookups, which is mild guidance. There is no explicit statement of when to call this instead of fiche_oeuvre, and no note that the id must first be obtained from a search tool.

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