Energy Podcast Digest

Read one episode

get_episode

Read-onlyIdempotent

One episode's title, show, summary, and full transcript. Scoped to episodes referenced by a published digest. Pass digest when an episode spans more than one week. Pass lang (es / zh) for the episode's translated title, summary, and transcript when the translations exist — lang in the payload echoes what was actually served ('' = English original).

Input Schema

TableJSON Schema

Name	Required	Description
`eid`	Yes	Episode id (from list_digest_episodes)
`lang`	No	Localized title + summary + transcript (es / zh); omit for English
`digest`	No	Optional YYYY-MM-DD edition date to disambiguate an episode that spans weeks

Output Schema

TableJSON Schema

Name	Required	Description
`eid`	Yes
`url`	Yes
`lang`	No	The language actually served ('' = English original)
`show`	Yes
`title`	Yes
`summary`	Yes
`chapters`	No	Chapter list (often empty): [{"start": seconds, "title": str}]
`speakers`	Yes
`published`	Yes
`transcript`	Yes
`description`	Yes	RSS episode description
`digest_slug`	Yes
`duration_sec`	Yes

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 title + summary + transcript (es / zh); omit for English",
+  "enum": [
+    "es",
+    "zh"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / lang

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

Changed2 schema fields changedSep 20, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / chapters

Added value: +{
+  "description": "Chapter list (often empty): [{\"start\": seconds, \"title\": str}]",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "description": {
+      "description": "RSS episode description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "digest_slug": {
+      "type": "string"
+    },
+    "duration_sec": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "eid": {
+      "type": "string"
+    },
+    "published": {
+      "type": "string"
+    },
+    "show": {
+      "type": "string"
+    },
+    "speakers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "transcript": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "eid",
+    "title",
+    "show",
+    "published",
+    "duration_sec",
+    "description",
+    "summary",
+    "transcript",
+    "speakers",
+    "digest_slug",
+    "url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 20, 2026
- changedInput schema / properties / eid / description
```
Previous value: -"Episode id"New value: +"Episode id (from list_digest_episodes)"
```
First observedSep 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world). The description adds real behavioral context: translations are only returned 'when the translations exist', and the 'lang' echo reveals what was actually served ('' = English original). This fallback/echo behavior is valuable and not derivable from annotations.

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?

Two front-loaded sentences: what is returned first, then parameter guidance. No wasted framing, though the parenthetical lang explanation is slightly dense.

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?

An output schema exists so return values need not be explained, and annotations carry safety. The description supplies scope, param conditions, and translation fallback behavior, leaving little for an agent to infer.

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 the baseline is 3. The description largely restates schema text (digest disambiguating cross-week episodes) and its 'es / zh' enumeration is out of sync with the schema enum that also lists 'hi' and 'fr', which could mislead an agent.

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 resource and enumerates the payload ('title, show, summary, and full transcript'), plus a scope constraint ('episodes referenced by a published digest'). The singular framing distinguishes it from list_digest_episodes without naming siblings explicitly.

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?

Gives clear conditions for optional params: pass 'digest' when an episode spans more than one week, pass 'lang' for translations. It does not explicitly name alternatives (get_digest, list_digest_episodes) or state when not to use it, so it stops short of a 5.

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?