Skip to main content
Glama
Opedd

Opedd

Official
by Opedd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read a licensed article

get_content
Read-onlyIdempotent

Retrieve the full body of a licensed Opedd article with a buyer API token. Use it for per-article or licence-order access; search-only licences cannot retrieve full text.

Instructions

Retrieve the full body of a licensed article using a buyer API token (opedd_buyer_live_* canonical; opedd_buyer_test_* for sandbox). Requires OPEDD_BUYER_TOKEN env var (create one at opedd.com/licenses after purchasing). Works for per-article Human republication licences and for licence orders: AI answers monthly and client display return full text. Your self-serve buyer API key reads articles under every order your account holds — no separate order token is needed. AI answers pay-per-request (including the self-serve licence) does NOT retrieve articles: it answers 403 SEARCH_ONLY_LICENCE — ask a question with search_passages instead. Articles the publisher stopped licensing answer 403 ARTICLE_EXCLUDED. The publisher must have content delivery enabled and must have pushed content for the article. Phase 11 M2 RAG-extended shape: response includes 7 RAG-essential metadata fields — author, language, word_count, content_hash, image_urls, canonical_url, tags. On pre-2026-05-14 historical articles, optional fields (author/language/image_urls/canonical_url/tags) may be NULL. NULL means 'data unavailable for this article', NOT 'explicitly empty' — treat as data-missing when filtering; do not interpret as anti-match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
article_idYesThe Opedd article UUID to retrieve content for
buyer_tokenNoBuyer API token (opedd_buyer_live_* or opedd_buyer_test_*). Falls back to OPEDD_BUYER_TOKEN env var.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.5

TDQS

A4.5/5.0
Behavior4/5

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

Adds significant context beyond annotations: token format, env var requirement, licence types, error codes, and NULL semantics for pre-2026-05-14 articles. Annotations already indicate read-only, idempotent, closed-world behavior, so this is thorough.

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

Conciseness3/5

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

Front-loaded with purpose but includes several dense parentheticals and error codes. It is informative but somewhat verbose and could be reorganized for better flow.

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 all critical context: authentication, licence applicability, error conditions, response shape, and NULL handling. No output schema, but it explains the RAG-extended response fields adequately.

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 already documents both parameters at 100% coverage. The description adds value by specifying token format (opedd_buyer_live_* / opedd_buyer_test_*) and env var fallback, plus the note that no separate order token is needed.

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?

Clearly states the specific action: retrieve the full body of a licensed article. It distinguishes itself from search_passages by noting that pay-per-request AI answers do not retrieve articles.

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 covers when to use (per-article Human republication licences, AI answers monthly, client display) and when not to use (AI answers pay-per-request → use search_passages). Also covers error conditions 403 SEARCH_ONLY_LICENCE and 403 ARTICLE_EXCLUDED.

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

Deploy Server

Other Tools