THC Open Mindfulness MCP

Find podcast episodes

find_podcast_episodes

Read-onlyIdempotent

Finds episodes of The Holistic Care Podcast: short episodes for parents, teachers and caregivers on children's emotional wellbeing, published in English ('en') and Hindi ('hi'). Examples: 'an episode about a child's anger', 'all Hindi episodes in season 2'. Filter with language and season; query matches every word against the episode title, summary and key question. Each result gives the episode's summary, duration, release date, the episode page (canonical_url) and the YouTube video (video_url). Transcripts and companion guides are not available through this server — link to the episode page instead. Use get_mindfulness_resource with resource_type 'podcast_episode' and an id such as 'PC-S02E03-EN' to fetch one episode.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`season`	No
`language`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: `query` matches every word against title, summary and key question (AND semantics), and that transcripts/companion guides are not served here. It loses a point only because the per-result field list partly duplicates the existing output schema.

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?

Purpose and language coverage are front-loaded, and the filtering, matching, availability and alternative-tool sentences each carry distinct information. It is denser than a minimal description ('Each result gives the episode's summary, duration, release date...' restates output-schema content), but nothing is padded or circular.

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?

With an output schema present, the description need not explain return shapes, yet it still covers domain, filters, matching semantics, known limitations and the handoff to get_mindfulness_resource. An agent has everything required to decide to call this tool and to construct a valid call.

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 description coverage is 0%, so the description carries the load, and it does so for three of four parameters: it enumerates the `language` values ('en', 'hi'), explains `season` as a filter, and defines `query` matching behavior and target fields. It never mentions `limit` (min 1, max 20), leaving that parameter documented only by its type constraints.

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 the specific resource (episodes of The Holistic Care Podcast), the audience/content scope (short episodes for parents, teachers and caregivers on children's emotional wellbeing), and the exact verb 'Finds'. It is immediately distinguishable from siblings like find_guided_practices or find_mindfulness_games without opening any schema.

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 gives concrete filtering guidance ('Filter with `language` and `season`'), clarifies the matching semantics of `query`, supplies worked examples ('all Hindi episodes in season 2'), states a limitation (transcripts and companion guides are not available through this server, link to the episode page instead), and routes the agent to the sibling get_mindfulness_resource with the exact resource_type and id format for single-episode retrieval.

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

All THC Open Mindfulness MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.