Skip to main content
Glama
Sign In

Opedd — Licensed Content for AI

by com.opedd
OverviewDiscussionsAdmin

Look up how an article is licensed

lookup_content
Read-onlyIdempotent

Looks up an article on Opedd by its web address. Returns the title, publication and how to license it (pay-per-answer search or a licence order); for a publication's homepage, the publication and its licensing page; for a publication that licenses directly, that it is available on request; or that it is not on Opedd yet (then request_publication records the request).

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>"
    },
    "name": "lookup_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe canonical URL of the article or content to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description is free to add real value — and it does, by spelling out four distinct response shapes (article licensing, publication homepage, direct-licensing publisher, not on Opedd). That is important behavioral disclosure given there is no output schema. It omits any mention of invalid/non-canonical URL handling or error behavior.

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-loaded with the core purpose and then branches into outcomes, with no filler. It is a single dense sentence with stacked semicolons, which is slightly harder to scan than a short bulleted outcome list would be.

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 one-parameter, read-only lookup with no output schema, the description covers the essential unknown — what comes back — via its enumerated outcome cases and the hand-off to request_publication. Remaining gaps are edge cases: invalid URLs, whether the URL must be canonical, and failure modes.

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% with a single parameter, so the baseline is 3. The description does add one piece of meaning beyond the schema: the URL may point at an article or at a publication's homepage, and the result differs accordingly — but it gives no canonicalization rules or format examples.

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?

States a specific verb and resource ("Looks up an article on Opedd by its web address") and enumerates the licensing-oriented outcomes, which separates it from browse_registry or search_content. It does not distinguish itself from verify_license or get_content, which an agent could plausibly confuse it with.

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 implied by the outcome list (check licence availability for a given URL) and it explicitly routes the not-yet-on-Opedd case to request_publication. However, it never states when to prefer this over verify_license, get_content, or place_licence_order, so the agent must infer the boundary.

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