Skip to main content
Glama
Sign In

Opedd — Licensed Content for AI

by com.opedd
OverviewDiscussionsAdmin

Ask to be told when a publication is available

request_publication
Idempotent

Asks Opedd to tell you when a publication it does not carry yet becomes available to license. For an article that lookup_content reports is not on Opedd. Records the request against the email given; nothing is bought. If the publication is already on Opedd, returns its licensing page instead; if it is listed as available on request, the request is passed to its publisher. Free; no key needed.

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": {
      "url": "<url>",
      "email": "<email>"
    },
    "name": "request_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe web address of the publication or of one of its articles.
nameNoOptional: the requester's name.
noteNoOptional: what the content is needed for (max 1000 characters).
emailYesWhere Opedd should write when the publication is available (the user's email, with their consent).
organizationNoOptional: the requester's company or fund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses that a request is recorded against the supplied email, that nothing is purchased, that the call is free, requires no key, and can silently resolve to a licensing page or a publisher hand-off instead of a request. What is left unsaid is behavior on a repeat request for the same publication, which matters given idempotentHint=true — hence a 4 rather than a 5.

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?

Purpose and the prerequisite check are front-loaded, then the side effects, then the branch cases — a sensible ordering with no filler. It is dense, packing five distinct facts into four sentences, but every sentence carries operational information.

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?

With five params (two required), full schema coverage, no output schema, and no nesting, this description covers everything an agent needs: what the call does, when it applies, what it writes, what it costs, and the two alternate return paths. Nothing material is missing for a tool of this complexity.

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 coverage is 100%, so url, email, name, note, and organization are already documented at the field level. The description reinforces where the email is used ('records the request against the email given') but adds no format, syntax, or edge-case guidance beyond the schema, 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?

The description gives a specific verb and resource: asking Opedd to notify when an un-carried publication becomes licensable. It explicitly frames itself as operating on material that 'lookup_content reports is not on Opedd,' which separates it from lookup_content and place_licence_order without opening any 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?

It states the triggering condition (publication not on Opedd), names the prerequisite check (lookup_content), and enumerates two exclusions with their alternate outcomes: already-on-Opedd returns a licensing page, on-request routes to the publisher. When-to-use, when-not, and the alternative are all explicit.

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