Skip to main content
Glama

Energy Podcast Digest

by io.energypod
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoYYYY-MM-DD edition date (from list_digests); omit for the latest

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
slugYesYYYY-MM-DD edition date
as_ofYes
sinceYes
versionYes
markdownYesThe full briefing (dossier) markdown
week_labelYes
episode_idsYes
episodes_urlYes
episode_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed2 schema fields changed
    • 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: +[]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as read-only and idempotent. The description adds useful behavioral context: omitting the slug returns the LATEST edition, and the response consists of markdown plus metadata. This goes beyond what annotations convey.

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 with no filler. The primary function is front-loaded, and the optional parameter behavior is stated efficiently. Every sentence contributes directly to correct invocation.

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 single-optional-parameter read tool with full schema coverage, an output schema, and safe annotations, the description is complete. It explains what the tool returns, how to target an edition, and the default behavior when no slug is supplied.

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 enhances the parameter semantics by clarifying that slug is the edition date from list_digests and that omission means 'latest', which adds practical meaning beyond the raw 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?

The description states a specific verb ('Read one edition') and resource ('a single edition'), and specifies what is returned ('full briefing markdown + metadata'). This clearly differentiates it from siblings like get_episode or list_digests.

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?

Provides clear context for use: retrieve a specific edition by its YYYY-MM-DD slug from list_digests, or omit it to get the latest. It doesn't explicitly state when not to use it compared to alternatives like get_episode, but the intended usage is well implied.

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 toolsInspect
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