Energy Podcast Digest

Read one edition

get_digest

Read-onlyIdempotent

Full briefing markdown + metadata for one edition. slug is the YYYY-MM-DD edition date from list_digests; omitting it returns the LATEST edition. The payload also carries export_html_url and export_pdf_url — pregenerated offline downloads of the edition ready to fetch. Pass region (the regional pilot, same as the site's ?region=) for a region's view: a generated per-region edition when one exists, else the master filtered to that region; regions in the payload lists what the edition offers.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Localized briefing (es / zh) when a translation exists; omit for English
`slug`	No	YYYY-MM-DD edition date (from list_digests); omit for the latest
`region`	No	Regional view of the briefing (na / emea / apac / latam); omit for the global edition

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`lang`	No	The language actually served ('' = English original)
`slug`	Yes	YYYY-MM-DD edition date
`as_of`	Yes
`since`	Yes
`region`	Yes	The applied regional view ('' = the global edition)
`regions`	Yes	The edition's available regional views
`version`	Yes
`markdown`	Yes	The full briefing (dossier) markdown
`week_label`	Yes
`episode_ids`	Yes
`region_note`	Yes	Set when a requested region filter emptied the view
`episodes_url`	Yes
`episode_count`	Yes
`export_pdf_url`	Yes	URL of the pregenerated offline PDF export (the same document, print-rendered)
`export_html_url`	Yes	URL of the pregenerated offline HTML export (a single self-contained file: briefing + bundled episode summaries)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "es",
-  "zh"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr"
+]

Changed2 schema fields changedOct 13, 2026

addedInput schema / properties / lang

Added value: +{
+  "description": "Localized briefing (es / zh) when a translation exists; omit for English",
+  "enum": [
+    "es",
+    "zh"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / lang

Added value: +{
+  "description": "The language actually served ('' = English original)",
+  "type": "string"
+}

Changed5 schema fields changedOct 13, 2026

addedInput schema / properties / region

Added value: +{
+  "description": "Regional view of the briefing (na / emea / apac / latam); omit for the global edition",
+  "enum": [
+    "na",
+    "emea",
+    "apac",
+    "latam"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / region

Added value: +{
+  "description": "The applied regional view ('' = the global edition)",
+  "type": "string"
+}

addedOutput schema / properties / region_note

Added value: +{
+  "description": "Set when a requested region filter emptied the view",
+  "type": "string"
+}

addedOutput schema / properties / regions

Added value: +{
+  "description": "The edition's available regional views",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "slug",
-  "week_label",
-  "as_of",
-  "episode_count",
-  "url",
-  "since",
-  "version",
-  "markdown",
-  "episode_ids",
-  "episodes_url",
-  "export_html_url",
-  "export_pdf_url"
-]New value: +[
+  "slug",
+  "week_label",
+  "as_of",
+  "episode_count",
+  "url",
+  "since",
+  "version",
+  "region",
+  "region_note",
+  "regions",
+  "markdown",
+  "episode_ids",
+  "episodes_url",
+  "export_html_url",
+  "export_pdf_url"
+]

Changed3 schema fields changedOct 11, 2026

addedOutput schema / properties / export_html_url

Added value: +{
+  "description": "URL of the pregenerated offline HTML export (a single self-contained file: briefing + bundled episode summaries)",
+  "type": "string"
+}

addedOutput schema / properties / export_pdf_url

Added value: +{
+  "description": "URL of the pregenerated offline PDF export (the same document, print-rendered)",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "slug",
-  "week_label",
-  "as_of",
-  "episode_count",
-  "url",
-  "since",
-  "version",
-  "markdown",
-  "episode_ids",
-  "episodes_url"
-]New value: +[
+  "slug",
+  "week_label",
+  "as_of",
+  "episode_count",
+  "url",
+  "since",
+  "version",
+  "markdown",
+  "episode_ids",
+  "episodes_url",
+  "export_html_url",
+  "export_pdf_url"
+]

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "type": "string"
+    },
+    "episode_count": {
+      "type": "integer"
+    },
+    "episode_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "episodes_url": {
+      "type": "string"
+    },
+    "markdown": {
+      "description": "The full briefing (dossier) markdown",
+      "type": "string"
+    },
+    "since": {
+      "type": "string"
+    },
+    "slug": {
+      "description": "YYYY-MM-DD edition date",
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "version": {
+      "type": "integer"
+    },
+    "week_label": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "week_label",
+    "as_of",
+    "episode_count",
+    "url",
+    "since",
+    "version",
+    "markdown",
+    "episode_ids",
+    "episodes_url"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 20, 2026

changedInput schema / properties / slug / description

Previous value: -"YYYY-MM-DD edition date"New value: +"YYYY-MM-DD edition date (from list_digests); omit for the latest"

changedInput schema / required

Previous value: -[
-  "slug"
-]New value: +[]

First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint=true, so the safety profile is known. The description adds valuable context about return data (markdown + metadata, export URLs) and the region fallback behavior, though it doesn't discuss rate limits or auth needs.

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?

The description is fairly dense but well-structured: front-loaded with purpose, then slug, then export, then region. Slightly long but each sentence adds value.

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?

Given the output schema exists, the description doesn't need to explain return values, but it still mentions key fields (export_html_url, export_pdf_url, regions). It covers parameter usage and fallback logic adequately for calling the tool correctly.

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. The description adds crucial details: slug is YYYY-MM-DD from list_digests, omitting returns latest, region is the regional pilot with fallback logic, and mentions the payload's 'regions' field. This goes beyond the schema.

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?

States a specific verb+resource: 'Full briefing markdown + metadata for one edition'. This clearly distinguishes it from the list/search siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains how to use the slug (from list_digests) and the fallback to the latest edition, which gives clear usage context. However, it doesn't explicitly say when to use this instead of get_episode or search, nor does it state exclusions.

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

All Energy Podcast Digest tools Inspect

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

Need Help?