Search KYMA369's public healing-frequency library by keyword, title, Hz value, or wellness intent (e.g. sleep, calm, focus, grounding). Returns matching frequency sets with play links.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1–20, default 8) | |
| query | Yes | Search text (title, description, Hz, or intent words) |
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?
No annotations are provided, so the description carries the burden. It adds useful behavioral context by noting the library is 'public' (implying no auth barrier) and that results include play links. It does not cover matching semantics or empty-result behavior, but 'Search' conveys a read-only operation.
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?
The description is a single focused sentence with the action front-loaded. Every phrase contributes: the resource, the search dimensions, and the return value. The examples are brief and useful rather than padding.
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?
For a low-complexity tool with two parameters and no output schema, the description covers the essentials: what is searched, what can be searched by, and what is returned. Some details like result ordering or exact response format are left to inference, but they are unlikely to block correct use.
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%, and both query and limit already have clear schema descriptions. The tool description adds only illustrative examples (sleep, calm, focus, grounding) rather than meaningful new parameter semantics, so the 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 states a specific action ('Search'), a precise resource ('KYMA369's public healing-frequency library'), and the supported search keys: keyword, title, Hz value, or wellness intent. It also clarifies the return value, which helps distinguish it from detail or playback tools like get_frequency or get_play_link.
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 sense of when to use the tool: whenever searching the healing-frequency library by text, Hz, or intent. It does not explicitly name sibling alternatives or state when not to use it, so it stops short of full routing guidance.
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.