Skip to main content
Glama

Opedd — Licensed Content for AI

by com.opedd
OverviewDiscussionsAdmin

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.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does a good job: it discloses the returned license key and certificate URL, the Handshake Email sent to the buyer, env var fallbacks, and the human-only restriction. It does not explicitly warn that the Stripe payment method will be charged or that the purchase is binding, but 'Purchase... using a Stripe payment method' strongly implies a financial transaction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each contributing useful information: purpose and return values, email notification, env var shortcuts, and licensing restrictions. The most important distinction is front-loaded, and there is no filler.

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 9-parameter purchase tool with no output schema, the description covers the essential return value, side effects, fallbacks, and the key alternative tool. It is not exhaustive about failure modes or irreversible charges, but the schema already documents every parameter and the description gives enough behavioral context for correct invocation.

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 the baseline is 3, but the description adds meaningful context beyond the schema: env var fallbacks for buyer_email and payment_method_id, the license key format, and the relationship between license_type and the alternative place_licence_order. This improves the agent's ability to populate parameters correctly.

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?

The description states a specific action ('Purchase a content license'), the protocol (Opedd), and the payment method (Stripe), and clearly distinguishes this tool from its sibling place_licence_order by explaining that AI licenses are handled elsewhere. The license key format and certificate URL add concrete outcome detail.

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?

The description explicitly routes AI license purchases to place_licence_order and states that single-article purchases are limited to the 'human' license type. This gives the agent clear criteria for choosing purchase_license over the closest alternative.

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