Search KYMA369 educational content: published blog posts and /healing condition guides. Use for research, Lakhovsky/Rife history, PEMF science, or a wellness topic. Returns titles, summaries, and URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Limit to blog articles, healing guides, or both (default all) | |
| limit | No | Max results (1–20, default 8) | |
| query | Yes | Topic, condition, or keyword (e.g. insomnia, PEMF, Lakhovsky, 40 Hz) |
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 provided, the description carries the full burden of behavioral disclosure. It adds useful facts: it searches only published content, covers blogs and guides, and returns titles, summaries, and URLs. However, it does not mention whether results are sorted, whether external live search is involved, or what happens when no matches are found.
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 compact and front-loaded: the verb, object, and content scope appear in the first sentence, followed by concrete use cases and return shape. Every sentence earns its place; there is no filler.
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 simple search tool with three well-documented parameters and no output schema, the description covers the essential caller needs: what is searched, which topics are relevant, and what the result contains. It could improve by noting sorting or empty-result behavior, but nothing critical is missing for correct invocation.
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 coverage is 100%, with each parameter already documented with examples and defaults. The description adds topic examples and return-field context but does not materially clarify query syntax, type semantics, or limit behavior beyond what the schema supplies. Baseline 3 is appropriate.
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 verb ('Search'), a clear resource ('KYMA369 educational content'), and the exact content types covered (published blog posts and healing condition guides). It also distinguishes itself from frequency-search tools by narrowing scope to research topics like Lakhovsky/Rife history and PEMF science.
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 provides explicit use cases ('Use for research, Lakhovsky/Rife history, PEMF science, or a wellness topic') that help an agent decide when to call it. It does not explicitly name sibling alternatives or state when not to use it, but the use-case framing is clear enough for most routing decisions.
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.