THC Open Mindfulness MCP

Get one mindfulness resource

get_mindfulness_resource

Read-onlyIdempotent

Fetches the full detail record for ONE specific, already-identified public resource — use this after search_mindfulness_resources or another find/search tool has surfaced a slug or id you now want the complete record for (e.g. a glossary term's full extended explanation, or a game's full description). For blog/mindfulness_game/guided_practice/research/glossary, identifier is the resource's slug. For panchavikas_pathway/panchavikas_download, identifier is the resource's stable id (e.g. 'PV-pathway-jal'), since that family has no slug. For podcast_episode, identifier is the episode id (e.g. 'PC-S02E03-EN'). A resource that does not exist and a resource that exists but is private behave identically here (a clean not-found result) — this tool never confirms or denies the existence of private content.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`identifier`	Yes	The resource's slug for blog/mindfulness_game/guided_practice/research/glossary. The resource's stable id (e.g. 'PV-pathway-jal') for panchavikas_pathway/panchavikas_download. The episode id (e.g. 'PC-S02E03-EN') for podcast_episode.
`resource_type`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`found`	Yes
`resource`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / identifier / description

Previous value: -"The resource's slug for blog/mindfulness_game/guided_practice/research/glossary. The resource's stable id (e.g. 'PV-pathway-jal') for panchavikas_pathway/panchavikas_download."New value: +"The resource's slug for blog/mindfulness_game/guided_practice/research/glossary. The resource's stable id (e.g. 'PV-pathway-jal') for panchavikas_pathway/panchavikas_download. The episode id (e.g. 'PC-S02E03-EN') for podcast_episode."

changedInput schema / properties / resource_type / enum

Previous value: -[
-  "blog",
-  "mindfulness_game",
-  "guided_practice",
-  "research",
-  "glossary",
-  "panchavikas_pathway",
-  "panchavikas_download"
-]New value: +[
+  "blog",
+  "mindfulness_game",
+  "guided_practice",
+  "research",
+  "glossary",
+  "panchavikas_pathway",
+  "panchavikas_download",
+  "podcast_episode"
+]

First observedSep 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover readOnly/idempotent/destructive/openWorld, but the description adds genuinely new behavior: private and non-existent resources produce an identical clean not-found, so the tool never leaks private-content existence. That is non-obvious, security-relevant semantics not present in any structured field.

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?

Front-loads the core purpose, then the usage trigger, then the identifier rules, then the privacy caveat in a logical order. It is somewhat long, but every sentence (especially the identifier mapping and privacy note) carries information an agent needs.

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?

For a two-param, read-only lookup with an output schema, the description covers selection, identifier format per resource_type, and edge-case behavior. Nothing needed to invoke it correctly is missing; return values are handled by the output schema.

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 50% (resource_type enum has no description), and the description compensates by mapping identifier semantics per resource_type family (slug vs stable id vs episode id) with examples. It largely mirrors the identifier schema description but adds the per-type rationale and example ids that make selection unambiguous.

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?

States a specific verb+resource ('fetches the full detail record for ONE specific resource') and explicitly positions it against search/find siblings. The agent immediately knows this is the single-record follow-up to a search, not a discovery tool.

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?

Explicitly says to use it 'after search_mindfulness_resources or another find/search tool has surfaced a slug or id', naming the alternatives and the triggering condition. It also gives the concrete payload expectation (full extended explanation, full game description).

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.