List top KYMA369 healing guides (condition-oriented frequency wellness pages). Prefer this when a human asks what to try for a symptom or goal.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max guides (1–25, default 12) |
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 must carry the burden. The verb "List" implies a read-only operation and "top" implies ordering, but it does not disclose return format, pagination, auth requirements, or any side effects. It is adequate for a simple list tool but not rich in behavioral context.
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, front-loaded sentence that communicates purpose and usage guidance without wasted words. Every phrase earns its place.
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 tool with one optional parameter and no output schema, the description covers the core purpose and usage trigger. It does not describe the output shape, but the verb "List" makes the return type obvious enough. Minor gaps around output details prevent a 5.
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% with the limit parameter fully documented in the input schema. The description adds no extra parameter meaning, so the baseline of 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 clear verb+resource: "List top KYMA369 healing guides," and adds specificity with "condition-oriented frequency wellness pages." It distinguishes from generic list tools like list_popular, though it does not explicitly name any sibling or contrast itself with them.
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 an explicit usage context: "Prefer this when a human asks what to try for a symptom or goal." This tells an agent when to choose it, but it does not mention when not to use it or name alternative sibling tools for exclusion.
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.