KAZM Mellow Mountain Radio

Tarot Card

get_tarot_card

Read-onlyIdempotent

Draws from the full 78-card Rider-Waite tarot deck. Returns the card of the day over Sedona (same for all listeners, turns at midnight MST), a single random draw, or a three-card past/present/future spread. Each card includes upright and reversed meanings, astrological correspondence, and suit element.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`spread`	No	daily = today's card of the day (deterministic, Sedona date); single = one random card; three = past/present/future. Defaults to daily.
`card_name`	No	Look up a specific card by name, e.g. 'The Tower' or 'Ten of Cups'. Returns full upright and reversed meanings.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No
`card`	No
`date`	No
`note`	No
`astro`	No
`cards`	No
`glyph`	No
`spread`	No
`upright`	No
`reversed`	No
`tarot_page`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds behavioral details: 'same for all listeners, turns at midnight MST' for daily spread, and that each card includes upright/reversed meanings, astrological correspondence, and suit element. No contradiction with annotations.

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?

Two sentences: first establishes deck and overall behavior, second details specific spread types and card output. No redundant information; every sentence adds value.

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?

Given the presence of an output schema, annotations, and schema descriptions, the description fully covers usage (spreads, card lookup), behavioral context (timezone, determinism), and return contents (meanings, astro, suit). No gaps for a tarot reading tool.

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 descriptions already explain parameters. Description adds context by elaborating on the spread enum values ('daily = today's card of the day (deterministic)...') and clarifying card_name usage ('Returns full upright and reversed meanings.'), enhancing beyond schema.

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?

Description specifies 'Draws from the full 78-card Rider-Waite tarot deck' and lists three distinct spreads (daily, single, three) plus card lookup, clearly distinguishing it from all sibling tools (none of which are tarot-related).

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?

Explains each spread type and the card_name parameter, implying appropriate use cases (daily for deterministic daily card, single/three for random draws, lookup for specific cards). Lacks explicit when-not-to-use or comparison to alternatives, but sibling differentiation is not needed as no other tarot tools exist.

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

All KAZM Mellow Mountain Radio tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation3/5

Tools are mostly distinct across categories (radio, local info, spiritual, listener management), but there is notable overlap: get_emergency_alerts and get_nws_alerts both provide alerts, and get_or_create_listener overlaps with register_listener. Also, get_chakra_frequencies, get_chakra_guide, and get_solfeggio are very similar. While descriptions help differentiate, agents may still struggle to select the right tool.

Naming Consistency5/5

All tool names consistently use lowercase snake_case with a verb_noun pattern (e.g., get_weather, submit_song_request, log_listener_history). The verbs are predictable (get, search, submit, log, register, update) and there are no deviations like camelCase or inconsistent verb styles.

Tool Count2/5

With 45 tools, the set is overgrown for a radio station server. Many tools are hyper-specific (e.g., separate tools for chakra frequencies, guide, and solfeggio; moon phase, sun times, and stargazing conditions). Consolidating similar functions would reduce cognitive load and improve coherence.

Completeness3/5

The tool set covers a broad range: radio operations, listener management, local news/weather, outdoor guides, spiritual content, etc. However, there are notable gaps: no tool to fetch full news articles (only headlines), no way to manage show schedules, and no donation or station info tools. Also, listener profile management is split across multiple tools, which feels incomplete.

Tarot Card

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources