Skip to main content
Glama

Get one moment

get_moment
Read-onlyIdempotent

One moment in full, by its slug (from search results) or its realalpha.app/s/ link: the speaker and what they do, the show and date, their quote, the summary and takeaways, its topics, the big questions it answers and how, and the episode's other best minutes. Use it to read a moment closely before quoting it, or when someone shares a realalpha.app/s/ link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_moment"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe moment's slug, like "ai-is-widening-the-gap-between-startups-and-incumbents", or its page's link

Output Schema

NameRequiredDescriptionDefault
urlYesThe moment's page, which plays the episode from it: the link to cite
citeYesA line to credit it by
dateYesWhen the episode came out, YYYY-MM-DD
showYes
slugYesThe moment's id, for get_moment
quoteNoTheir words, as said in the episode
titleYes
lengthYes
topicsYes
answersYesThe big questions it answers, which way, and what the speaker says
episodeYes
speakerNoWho's talking
summaryYes
show_pageYes
starts_atYesWhere in the episode it starts, like 31:50
takeawaysYesThe moment's main points
episode_urlYesThe episode's page, from the moment on
speaker_pageNoTheir page on realalpha.app, with every moment of theirs
speaker_roleNoWhat they do
more_from_the_episodeYesThe episode's other best minutes

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": {
      +    "answers": {
      +      "description": "The big questions it answers, which way, and what the speaker says",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "question": {
      +            "type": "string"
      +          },
      +          "question_id": {
      +            "description": "For answers_to",
      +            "type": "string"
      +          },
      +          "says": {
      +            "type": "string"
      +          },
      +          "stance": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "question",
      +          "question_id",
      +          "stance",
      +          "says"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "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"
      +    },
      +    "more_from_the_episode": {
      +      "description": "The episode's other best minutes",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "starts_at": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "starts_at",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "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"
      +    },
      +    "takeaways": {
      +      "description": "The moment's main points",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "topics": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "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",
      +    "takeaways",
      +    "topics",
      +    "answers",
      +    "more_from_the_episode"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the bar is lower. Beyond that, the description discloses that the same tool accepts either a bare slug or a full page URL, and it characterizes the depth of the returned record ('in full', 'the episode's other best minutes'). It does not say what happens with a malformed or unknown slug, which is the one notable omission.

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 definition is front-loaded with the resource and the input contract, then the payload, then the use cases — a sensible order. It is a single dense sentence with a long enumerative middle, so it reads as a list rather than crisp prose, but no sentence is wasted.

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 the description need not enumerate return fields, yet its enumeration usefully signals retrieval depth for tool selection rather than duplicating schema detail. For a single-parameter read tool with full annotation coverage, the only missing piece an agent might want is failure behavior on an invalid slug.

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% and the single slug parameter is already documented with an example, so the schema carries the weight. The description adds only the concrete link form (realalpha.app/s/) as an alternative input, which is marginal extra meaning beyond the schema's 'or its page's link'. Baseline 3 is appropriate for a one-parameter tool with full coverage.

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-and-resource pair ('One moment in full') and immediately scopes it to retrieval by slug or by a realalpha.app/s/ link. The 'in full' phrasing plus the 'from search results' parenthetical implicitly separates it from the list-style siblings (search_moments, latest_moments), which return partial records. An agent can tell what it gets back without opening the 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?

It gives two concrete use conditions: reading a moment closely before quoting it, and following a shared realalpha.app/s/ link. That is real when-to-use guidance rather than an implied purpose. It stops short of an explicit exclusion (e.g., 'do not use this to browse or search'), so it does not reach the top band.

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