Skip to main content
Glama

Opedd — Licensed Content for AI

by com.opedd

list_feed

List articles from a buyer's licensed catalog via GET /enterprise-license (Phase 10 + 11). Content contract: flat-fee scopes (custom/platform_wide) include full content_body; METERED (filtered-scope) keys get a discovery-only feed — content_body is null and content_access is 'metered_per_call'; fetch article text via get_content (each retrieval is billed). Returns JSON-format response with paginated articles. Use since (ISO 8601) for delta-feed polling — only articles published after the timestamp. Use cursor for pagination across pages. Requires OPEDD_ACCESS_KEY (ent_* enterprise access key). For larger bulk corpus pulls, use stream_feed_ndjson (up to 1000 articles per call vs 200 here).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax articles per response (default: 50, max: 200)
sinceNoISO 8601 timestamp — return only articles with published_at > since
cursorNoOpaque cursor from the prior response's data.pagination.next_cursor

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: metered keys get discovery-only feed with null content_body and 'metered_per_call' access, retrieval via get_content is billed, requires OPEDD_ACCESS_KEY, and returns paginated JSON. This is rich, non-obvious context beyond what any schema could convey.

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?

Dense but efficient; each sentence carries distinct info (endpoint, content contract, params, auth, alternative). Slightly long, but every clause adds value and the structure is logical.

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?

Covers purpose, response format, authentication, pagination, delta polling, metered behavior, and alternative. Given no output schema and no annotations, this description provides sufficient context for an agent to use the tool correctly without further clarification.

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%, but the description adds important semantic context: `since` is for delta-feed polling, `cursor` is an opaque token from the response's data.pagination.next_cursor, and `limit` has a max of 200. This goes beyond the schema descriptions, which are already good.

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 clearly states 'List articles from a buyer's licensed catalog via GET /enterprise-license' — a specific verb, resource, and endpoint. It also differentiates from sibling tools like get_content and stream_feed_ndjson by describing the distinct behavior for metered keys and bulk pulls.

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?

Provides explicit usage context: `since` for delta-feed polling, `cursor` for pagination, and a direct alternative for bulk pulls ('use stream_feed_ndjson'). This gives clear guidance on when to use this tool versus alternatives.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have distinct purposes, but list_feed and stream_feed_ndjson both list licensed articles (with different formats), and browse_registry vs publisher_directory could confuse agents about scope. Overall, the set is mostly clear.

Naming Consistency4/5

Names follow a verb_noun pattern with underscores (e.g., get_content, purchase_license). A few outliers like rsl_get and article_53_attestation break the pattern slightly, but the majority are consistent.

Tool Count4/5

17 tools cover buyer, publisher, and discovery workflows. While slightly above the typical 3-15 range, the complexity of the licensing platform justifies the count. No tool seems redundant.

Completeness4/5

The tool set covers discovery, purchase, content retrieval, compliance, and attestation comprehensively. Minor gaps like missing license management or key rotation are acceptable given the domain scope.

Resources