Skip to main content
Glama

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.

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": "get_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLocalized briefing in any supported language; omit for English
slugNoYYYY-MM-DD edition date (from list_digests); omit for the latest
regionNoRegional view of the briefing (na / emea / apac / latam); omit for the global edition

Output Schema

NameRequiredDescriptionDefault
urlYes
langNoThe language actually served ('' = English original)
slugYesYYYY-MM-DD edition date, or SE-YYYY-MM-DD for a special edition
as_ofYes
sinceYes
regionYesThe applied regional view ('' = the global edition)
regionsYesThe edition's available regional views
versionYes
markdownYesThe full briefing (dossier) markdown
week_labelYescanonical ISO week label (Week 45 · 2026)
episode_idsYes
region_noteYesSet when a requested region filter emptied the view
episodes_urlYes
edition_labelNopublic edition title; a special edition's own name
episode_countYes
export_pdf_urlYesURL of the pregenerated offline PDF export (the same document, print-rendered)
export_html_urlYesURL of the pregenerated offline HTML export (a single self-contained file: briefing + bundled episode summaries)
special_editionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / 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"
  2. Changed3 schema fields changed
    • addedOutput schema / properties / edition_label
      Added value: +{
      +  "description": "public edition title; a special edition's own name",
      +  "type": "string"
      +}
    • addedOutput schema / properties / special_edition
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / week_label / description
      Added value: +"canonical ISO week label (Week 45 · 2026)"
  3. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Localized briefing (es / zh) when a translation exists; omit for English"New value: +"Localized briefing in any supported language; omit for English"
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "es",
      -  "zh",
      -  "hi",
      -  "fr",
      -  "ar"
      -]New value: +[
      +  "es",
      +  "zh",
      +  "hi",
      +  "fr",
      +  "ar",
      +  "pt",
      +  "ja"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Localized briefing in any supported language; omit for English"New value: +"Localized briefing (es / zh) when a translation exists; omit for English"
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "es",
      -  "zh",
      -  "hi",
      -  "fr",
      -  "ar",
      -  "pt"
      -]New value: +[
      +  "es",
      +  "zh",
      +  "hi",
      +  "fr",
      +  "ar"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Localized briefing (es / zh) when a translation exists; omit for English"New value: +"Localized briefing in any supported language; omit for English"
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "es",
      -  "zh",
      -  "hi",
      -  "fr",
      -  "ar"
      -]New value: +[
      +  "es",
      +  "zh",
      +  "hi",
      +  "fr",
      +  "ar",
      +  "pt"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "es",
      -  "zh",
      -  "hi",
      -  "fr"
      -]New value: +[
      +  "es",
      +  "zh",
      +  "hi",
      +  "fr",
      +  "ar"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "es",
      -  "zh"
      -]New value: +[
      +  "es",
      +  "zh",
      +  "hi",
      +  "fr"
      +]
  8. Changed2 schema fields changed
    • 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"
      +}
  9. Changed5 schema fields changed
    • 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"
      +]
  10. Changed3 schema fields changed
    • 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"
      +]
  11. 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"
      +}
  12. 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: +[]
  13. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already establish a safe, idempotent, closed-world read, so the bar is lower. The description still adds real behavioral context beyond them: the payload carries pregenerated offline `export_html_url`/`export_pdf_url` downloads, and `region` falls back to a master edition filtered to that region when no per-region edition exists — a non-obvious resolution rule.

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 payload is stated first, then default behavior, then the region mechanics — well front-loaded with no filler sentences. The density of clauses around `region` is high, and the mixed backtick/double-backtick markup is slightly noisy, but nothing is expendable.

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 tool with three optional, fully described parameters, an output schema, and rich annotations, the description covers what it must: default behavior with no slug, how to get a regional view, and where slugs come from. Return-format detail is correctly left to 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?

Schema coverage is 100%, so 3 is the baseline. The description earns above that by explaining what `region` actually means — the regional pilot matching the site's ?region= — and by disclosing the generated-vs-filtered fallback plus the `regions` field in the payload. It does not elaborate on `lang`, which the schema fully handles.

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 opening sentence names a specific resource and payload: 'Full briefing markdown + metadata for one edition.' It also ties the tool to its sibling by stating that `slug` comes from list_digests, so an agent can distinguish this read-one tool from the list tool without opening a schema.

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?

The description gives clear selection logic for its optional parameters: omit `slug` for the latest edition, pass `region` for a regional view, and it names list_digests as the source of valid slugs. It stops short of explicitly excluding or contrasting with get_episode/get_digest_episodes, so it is clear context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources