Skip to main content
Glama

Ask the transcripts a question

ask_question

Starts a cited answer drawn only from what was said on podcasts, or from one episode when episode_id (the pid of a search result) is given. Returns a job_id; call get_answer with it until status is complete (usually under a minute). Needs an API key; billed per question (see list_services).

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

Input Schema

NameRequiredDescriptionDefault
questionYes
episode_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / episode_id
      Added value: +{
      +  "format": "uuid",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses that this is an asynchronous job with a job_id, an expected latency ('usually under a minute'), an authentication requirement ('needs an API key'), and a monetary cost ('billed per question') with a pointer to list_services for pricing. These are exactly the operational facts an agent needs before invoking a paid, non-idempotent operation.

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?

Three dense sentences, front-loaded with the action and scope, then the async contract, then cost and auth. Every clause carries information; nothing is redundant with the title or schema.

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?

For an async, paid tool with no output schema, the description covers the return value (job_id), the polling path, latency, and billing, which is nearly everything needed to call it correctly. It could say more about what a completed answer looks like (citation format, failure states), but the essentials are present.

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 description coverage is 0%, so the description must carry the load. It explains episode_id well, tying it to 'the pid of a search result', which tells the agent where the value comes from. It adds nothing about the question parameter's constraints (3-500 characters) or the uuid format, leaving part of the compensation gap unfilled.

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 states a specific verb and resource ('starts a cited answer drawn only from what was said on podcasts') and distinguishes the two scopes: whole corpus versus a single episode when episode_id is supplied. It also names the follow-up tool get_answer, which separates it from one-shot siblings like search_transcripts or get_transcript, though it never explicitly contrasts with those siblings.

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 clear when-to-use context (asking a question across podcast transcripts, or narrowing to one episode) and prescribes the follow-up loop: call get_answer with the returned job_id until status is complete. It stops short of stating when NOT to use it, e.g. when a simple keyword lookup via search_transcripts would suffice.

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