Skip to main content
Glama

How AI leaders answer a big question

answers_to
Read-onlyIdempotent

How the people building AI answer one of the big questions people ask about it, from the moments Real Alpha cut: grouped by which way they answer, the biggest group first, each with what the speaker says, who they are, the show and date. Use it when someone asks where AI leaders stand on one of these questions; for any other question, search_moments. The questions: is-ai-a-bubble (Is AI a bubble?); which-jobs-will-ai-replace (Which jobs will AI replace, and which are safe?); will-ai-replace-software-engineers (Will AI replace software engineers?); will-ai-replace-doctors (Will AI replace doctors?); will-ai-replace-lawyers (Will AI replace lawyers?); is-saas-dead (Is SaaS dead?); when-will-we-get-agi (When will we get AGI?); is-openai-profitable (How does OpenAI make money, and is it profitable?); ai-predictions (What will AI look like in the next few years?); are-ai-agents-ready (Are AI agents ready for real work?); is-ai-paying-off (Is AI paying off for companies?); is-ai-dangerous (Is AI dangerous?); will-ai-make-cyberattacks-worse (Will AI make cyberattacks worse?); can-anyone-compete-with-nvidia (Can anyone compete with Nvidia?); is-there-a-gpu-shortage (Is there still a GPU shortage?); is-there-enough-power-for-ai (Is there enough power for AI?); is-moores-law-dead (Is Moore’s law dead?); is-ai-progress-slowing (Is AI progress slowing down?); is-open-source-ai-catching-up (Is open-source AI catching up?); is-china-catching-up-in-ai (Is China catching up in AI?); is-ai-overhyped (Is AI overhyped?); will-ai-replace-google-search (Will AI replace Google search?); is-vibe-coding-the-future (Is vibe coding the future?); is-a-computer-science-degree-worth-it (Is a computer science degree still worth it?); are-ai-wrappers-a-real-business (Are AI wrappers a real business?); how-do-ai-companies-make-money (How do AI companies make money?); should-ai-be-regulated (Should AI be regulated?); will-ai-cure-diseases (Will AI cure diseases?); when-will-humanoid-robots-be-useful (When will humanoid robots be useful?); are-self-driving-cars-safe (Are self-driving cars safe?); will-ai-boost-economic-growth (Will AI boost economic growth?); will-ai-replace-accountants (Will AI replace accountants?); will-ai-replace-teachers (Will AI replace teachers?); will-ai-replace-customer-service (Will AI replace customer service jobs?).

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": {
      "question": "<question>"
    },
    "name": "answers_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe question's id, like "is-ai-a-bubble"

Output Schema

NameRequiredDescriptionDefault
tipNoWhat to try when nothing matched
pageNoThe question's page on realalpha.app, once enough moments answer it
groupsYesThe moments by which way they answer, the biggest group first
questionYes
answered_byYesHow many moments answer it

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": {
      +    "answered_by": {
      +      "description": "How many moments answer it",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "groups": {
      +      "description": "The moments by which way they answer, the biggest group first",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "count": {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          "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"
      +                },
      +                "says": {
      +                  "description": "The speaker's answer, in a few words",
      +                  "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": [
      +                "says",
      +                "slug",
      +                "title",
      +                "show",
      +                "show_page",
      +                "episode",
      +                "date",
      +                "summary",
      +                "starts_at",
      +                "length",
      +                "url",
      +                "episode_url",
      +                "cite"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "stance": {
      +            "description": "Which way they answer",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "stance",
      +          "count",
      +          "moments"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "page": {
      +      "description": "The question's page on realalpha.app, once enough moments answer it",
      +      "type": "string"
      +    },
      +    "question": {
      +      "type": "string"
      +    },
      +    "tip": {
      +      "description": "What to try when nothing matched",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "question",
      +    "answered_by",
      +    "groups"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety needs no restating. The description adds genuine behavioral context beyond that: results are clustered by answer stance and ordered by group size, and each entry carries a quote, attribution, show and date. It doesn't discuss empty results for sparse questions or result-size limits, which keeps it short of a 5.

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

Conciseness3/5

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

The purpose and routing guidance are correctly front-loaded in the first two sentences. However, the trailing enumeration of 34 id/question pairs is bulky and largely repeats the enum verbatim, so the description is dominated by a list that only partly earns its length.

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 return values need not be explained, yet the description still previews the grouping and per-entry fields usefully. For a single-enum-parameter query tool with full annotations, this covers everything an agent needs to select and invoke it; only guidance on sparse or empty questions is absent.

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% and the enum already lists every valid id, so the schema carries the baseline. The description nevertheless adds real meaning by glossing each id as the natural-language question it answers, which is what lets an agent map a user's phrasing onto a valid enum value.

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 names a specific resource (how AI leaders answer a given big question) and specifies the shape of the result: quotes grouped by answer position, largest group first, each with speaker, show and date. This is clearly distinguishable from sibling retrieval tools like search_moments.

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?

It states the triggering condition ("Use it when someone asks where AI leaders stand on one of these questions") and an explicit exclusion with a named alternative ("for any other question, search_moments"). That is exactly the when/when-not/alternative structure the highest score requires.

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