Skip to main content
Glama

Opedd — Licensed Content for AI

by com.opedd
OverviewDiscussionsAdmin

Buy an article licence

purchase_license

Purchase a content license from the Opedd protocol using a Stripe payment method. Returns a license key (format: OP-XXXX-XXXX) and a certificate URL. The buyer receives a Handshake Email with their license key. Set OPEDD_BUYER_EMAIL and OPEDD_PAYMENT_METHOD_ID env vars to avoid passing them on every call. Single-article purchases are Human republication licences only (license_type 'human'). AI licences (AI answers, AI training, client display) are bought as licence orders: see place_licence_order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
article_idNoOpedd article UUID (use this OR article_url)
buyer_nameNoFull name of the buyer (for the license record and certificate)
article_urlNoURL of the article to license (use this OR article_id)
buyer_emailNoEmail address for the license. Falls back to OPEDD_BUYER_EMAIL env var.
intended_useNoIntended use of the licensed content
license_typeYeshuman = Human republication (editorial republication of one article)
terms_acceptedYesREQUIRED. Set true only after the buyer (your principal) has accepted the Opedd licence terms at opedd.com/terms. The acceptance timestamp is recorded with the licence; purchases without genuine acceptance are rejected.
payment_method_idNoStripe payment method ID (pm_...). Falls back to OPEDD_PAYMENT_METHOD_ID env var.
buyer_organizationNoOrganization or company name (for enterprise/editorial licenses)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / license_type / description
      Previous value: -"human = republication/editorial rights, ai = training dataset rights, ai_inference = inference/RAG rights"New value: +"human = Human republication (editorial republication of one article)"
    • changedInput schema / properties / license_type / enum
      Previous value: -[
-  "human",
-  "ai",
-  "ai_inference"
-]New value: +[
+  "human"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / terms_accepted
      Added value: +{
+  "description": "REQUIRED. Set true only after the buyer (your principal) has accepted the Opedd licence terms at opedd.com/terms. The acceptance timestamp is recorded with the licence; purchases without genuine acceptance are rejected.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "license_type"
-]New value: +[
+  "license_type",
+  "terms_accepted"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), and the description adds useful behavior beyond them: the returned license key format, certificate URL, and the Handshake Email delivery. It stops short of warning that, given idempotentHint=false, a retried call likely creates a second charge — a notable omission for a payment tool, keeping it out of 5 territory.

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?

Front-loads the action and payment mechanism, then layers returns, side effects, and the sibling routing in a tight sequence. Every sentence carries information, though the env-var sentence slightly overlaps with schema content.

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?

With no output schema, the description usefully compensates by naming what comes back (license key, certificate URL) and the out-of-band Handshake Email. Combined with explicit sibling routing for AI licences, an agent has enough to call correctly, though the retry/duplicate-charge risk of a non-idempotent purchase is unaddressed.

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 100%, so all 9 parameters including env-var fallbacks and the terms_accepted semantics are already documented in the schema. The description restates the env-var fallbacks (OPEDD_BUYER_EMAIL, OPEDD_PAYMENT_METHOD_ID) rather than adding new meaning, so the baseline 3 applies.

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 ('Purchase a content license from the Opedd protocol'), names the payment rail (Stripe), and adds concrete outputs (license key OP-XXXX-XXXX, certificate URL). It also draws a hard boundary against the sibling place_licence_order for AI licence types, so an agent can route correctly without opening either 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?

Explicitly scopes the tool to single-article Human republication licences (license_type 'human') and tells the agent to use place_licence_order for AI licences, which is its closest sibling. It also flags the env-var shortcut (OPEDD_BUYER_EMAIL, OPEDD_PAYMENT_METHOD_ID) so callers know what need not be passed each time.

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

All Opedd — Licensed Content for AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources