Skip to main content
Glama

Latest moments

latest_moments
Read-onlyIdempotent

The newest moments Real Alpha cut, newest episode first: each episode's best minutes, from every show or only one. Use it when someone asks what's new in AI this week from the people building it, what AI leaders have said lately, or what's new on a show.

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

Input Schema

NameRequiredDescriptionDefault
nNoHow many, 10 if not given, 20 at most
showNoOnly from this show: "Lenny's Podcast"

Output Schema

NameRequiredDescriptionDefault
momentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "moments": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "cite": {
      +            "description": "A line to credit it by",
      +            "type": "string"
      +          },
      +          "date": {
      +            "description": "When the episode came out, YYYY-MM-DD",
      +            "type": "string"
      +          },
      +          "episode": {
      +            "type": "string"
      +          },
      +          "episode_url": {
      +            "description": "The episode's page, from the moment on",
      +            "type": "string"
      +          },
      +          "length": {
      +            "type": "string"
      +          },
      +          "quote": {
      +            "description": "Their words, as said in the episode",
      +            "type": "string"
      +          },
      +          "show": {
      +            "type": "string"
      +          },
      +          "show_page": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "The moment's id, for get_moment",
      +            "type": "string"
      +          },
      +          "speaker": {
      +            "description": "Who's talking",
      +            "type": "string"
      +          },
      +          "speaker_page": {
      +            "description": "Their page on realalpha.app, with every moment of theirs",
      +            "type": "string"
      +          },
      +          "speaker_role": {
      +            "description": "What they do",
      +            "type": "string"
      +          },
      +          "starts_at": {
      +            "description": "Where in the episode it starts, like 31:50",
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "The moment's page, which plays the episode from it: the link to cite",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "title",
      +          "show",
      +          "show_page",
      +          "episode",
      +          "date",
      +          "summary",
      +          "starts_at",
      +          "length",
      +          "url",
      +          "episode_url",
      +          "cite"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "moments"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavioral context: results are ordered newest episode first and consist of each episode's 'best minutes.' It does not discuss result volume beyond the n cap or how 'best minutes' are selected.

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 sentences: the first defines the resource and ordering, the second lists usage triggers. Front-loaded and largely waste-free, though the opening clause is slightly convoluted and could name the resource more plainly.

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?

With an output schema present and both parameters fully documented, the description only needs to convey what the tool returns and when to call it, which it does. Ordering and show-filtering behavior are stated; nothing essential for correct invocation is missing.

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%, with defaults and the max of 20 already documented in the schema. The phrase 'from every show or only one' reinforces that the show parameter is an optional filter rather than a requirement, which is a small value-add over the schema. Baseline 3 is appropriate.

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?

The description names a specific resource (moments) and its scope: the newest clips from Real Alpha episodes, ordered newest-episode-first, sourced from all shows or one. It implicitly contrasts with search_moments by framing everything as recency-driven. The only weakness is product-specific jargon ('moments Real Alpha cut') that requires some inference about what a 'moment' actually is.

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 gives concrete triggering intents -- 'what's new in AI this week,' 'what AI leaders have said lately,' 'what's new on a show' -- which map well to typical requests. It does not explicitly say when to prefer search_moments or what_did_they_say instead, so the routing against siblings is left partly to inference.

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.