Energy Podcast Digest

List editions

list_digests

Read-onlyIdempotent

Newest-first list of every published energypod.io edition (weekly energy-industry digests): slug (YYYY-MM-DD), week label, and episode count. Call this FIRST — the first entry is the latest week, and its slug feeds get_digest / list_digest_episodes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_digests"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`digests`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedOutput schema / properties / digests / items / properties / slug / description

Previous value: -"YYYY-MM-DD edition date"New value: +"YYYY-MM-DD edition date, or SE-YYYY-MM-DD for a special edition"

Changed3 schema fields changedNov 7, 2026
- addedOutput schema / properties / digests / items / properties / edition_label
```
Added value: +{
+  "description": "public edition title; a special edition's own name",
+  "type": "string"
+}
```
- addedOutput schema / properties / digests / items / properties / special_edition
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / digests / items / properties / week_label / description
```
Added value: +"canonical ISO week label (Week 45 · 2026)"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "digests": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "as_of": {
+            "type": "string"
+          },
+          "episode_count": {
+            "type": "integer"
+          },
+          "slug": {
+            "description": "YYYY-MM-DD edition date",
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "week_label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "week_label",
+          "as_of",
+          "episode_count",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "digests"
+  ],
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond that: results are ordered newest-first and entry zero is the most recent week. It does not discuss pagination or result size limits, which keeps it just short of a 5 for a zero-parameter listing tool.

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

Conciseness5/5

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

Two sentences, zero filler, with the result shape front-loaded and the orchestration instruction second. The slug format hint (YYYY-MM-DD) is compact and directly actionable.

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?

For a parameterless listing tool with an output schema and full annotation coverage, this description supplies everything an agent needs: what it returns, ordering, and its role as the entry point for the digest tools. Additional detail would be redundant against the output schema.

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?

There are no input parameters, so the baseline is 4. The description correctly adds no parameter documentation, and instead spends its words on output shape, which is the only meaningful semantic surface here.

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 and resource ('Newest-first list of every published energypod.io edition'), clarifies what an edition is (weekly energy-industry digest), and enumerates the returned fields (slug with YYYY-MM-DD format, week label, episode count). An agent can distinguish it from get_digest and list_digest_episodes without opening any schema.

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?

Gives explicit sequencing guidance ('Call this FIRST') and explains why: the first entry is the latest week and its slug feeds get_digest / list_digest_episodes. It names the downstream siblings and the exact value that connects them, leaving nothing to inference.

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?