Return the canonical KYMA encyclopedia URL for a named Hz or hub (e.g. 432, 528, 7.83, 40, sleep-frequencies, solfeggio-frequencies). Use this instead of inventing Hz facts.
| Name | Required | Description | Default |
|---|---|---|---|
| hz | Yes | Hz number or hub id (432, 528, 7.83, sleep-frequencies, rife-frequencies, …) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden, and it does disclose the core behavior: returning a canonical URL and steering agents away from inventing facts. However, it omits any details about the response format, potential errors, or page-not-found behavior, which would add transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences front-load the tool's purpose and provide a practical guardrail, with zero filler. Every part of the description adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one parameter, no output schema, no annotations), and the description covers the purpose, parameter examples, and the behavioral guardrail. It lacks explicit failure-mode or return-format details, but for a single-purpose URL lookup the description is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameter is already documented with examples ('Hz number or hub id'). The description reiterates these examples and adds the notion of a 'named' hub, but does not materially expand on the schema's meaning, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies a specific verb and resource ('Return the canonical KYMA encyclopedia URL') with concrete examples, making the tool's purpose unmistakable. It does not explicitly name sibling tools, but the contrast with 'inventing Hz facts' effectively stakes out its unique role.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear directive to use this tool when a canonical URL is needed rather than hallucinating information, but it does not explicitly compare this tool to sibling tools like get_frequency or compare_frequencies. Usage is implied rather than explicitly routed against alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a mostly distinct action: fetching exact frequency sets, searching, building play links, checking hardware requirements, and listing guides. Minor overlap exists between get_frequency and get_play_link since get_frequency already returns a play link, but descriptions clarify the different entry points.
Most names follow a clear verb_noun pattern: compare_frequencies, get_frequency, get_hz_page, get_play_link, list_healing_guides, list_popular, search_content, search_frequencies. A few exceptions like about_kyma and headphones_or_pemf break the pattern slightly but are still readable and predictable.
Ten tools is well-scoped for a frequency wellness content server. Each tool serves a distinct part of the user journey: product awareness, research, search, frequency lookup, playback, and hardware guidance.
The surface covers the core read-only workflows well: discovering frequencies, looking up canonical pages, comparing options, getting playback links, and finding healing guides. A minor gap is the lack of a dedicated tool for fetching a full healing guide body, but search/list results include URLs and summaries, so agents can still work around it.