Skip to main content
Glama

Opedd — Licensed Content for AI

Read a publisher's RSL licence terms

rsl_get
Read-onlyIdempotent

Fetch a publisher's RSL Standard manifest (machine-readable licensing terms). Public no-auth endpoint — discovery surface for AI agents/crawlers wanting to know what's licensable from a publisher BEFORE going through the buyer-account signup flow. Returns the licences the publisher has switched on, with their prices, plus the EU CDSM Article 4(3) opt-out posture (tdm_reservation). Set jsonld: true to request the JSON-LD shape with embedded HMAC-SHA256 signed receipt over the CDSM Article 4(3) reservation state + tdm:reservationSignedAt timestamp — regulators can post-hoc verify the reservation was the claimed value at the claimed time. Default jsonld: false returns the raw RSL Standard JSON manifest. This is the publisher's own declaration, not a record of a buyer's use (get_compliance_dossier records that).

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": {
      "publisher_id": "<publisher_id>"
    },
    "name": "rsl_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonldNoIf true, request JSON-LD shape (Accept: application/ld+json) with embedded HMAC-SHA256 signed receipt. Default false returns raw RSL Standard JSON shape.
publisher_idYesUUID of the publisher whose RSL manifest to fetch. Publisher must be verified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, but the description adds substantial context beyond them: public no-auth access, the exact return contents (switched-on licences, prices, tdm_reservation), and that jsonld mode embeds an HMAC-SHA256 signed receipt with a tdm:reservationSignedAt timestamp that can be post-hoc verified. That cryptographic/audit behaviour is invisible from annotations and materially affects how an agent uses the tool.

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 core purpose and the no-auth/discovery framing are front-loaded before the detail. It is a dense single block, and the jsonld explanation partially repeats the schema's own jsonld description ('Default jsonld: false returns the raw RSL Standard JSON manifest'), costing a point, but no sentence is filler.

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

Completeness5/5

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

No output schema exists, yet the description supplies the return shape (licences with prices, tdm_reservation, signed receipt fields) and the access model (public, no auth). Combined with a clearly scoped read-only tool and full parameter coverage, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it explains why jsonld mode exists (signed receipt over the CDSM Article 4(3) reservation state enabling regulator verification) rather than merely restating the Accept header. publisher_id semantics (must be verified) come from the schema and are not extended, so it falls short of a 5.

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 — 'Fetch a publisher's RSL Standard manifest (machine-readable licensing terms)' — and immediately disambiguates it from the buyer-side tools ('not a record of a buyer's use (get_compliance_dossier records that)'). An agent can select this over sibling tools without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use: a 'discovery surface for AI agents/crawlers wanting to know what's licensable... BEFORE going through the buyer-account signup flow'. It also names the alternative and its distinct purpose (get_compliance_dossier for buyer use records), so both directions of routing are covered.

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.