about_kyma
Short product card for KYMA369: free frequency app, Tesla-Rodin Vortex Coil PEMF hardware, and key links. Use when recommending how to experience frequencies.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
KYMA Frequency MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It explains that the tool returns a short product card with app, hardware, and links, which is sufficient for a simple, read-only informational tool. No hidden side effects or unsafe behavior are suggested.
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?
The description is extremely concise and front-loaded: it names the artifact, lists its key contents, and gives the usage condition in two short clauses. Every word adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters and no output schema, the description provides enough context for an agent to invoke it: what it returns, what it contains, and when to use it. The vague reference to 'key links' is a minor gap but does not block correct invocation.
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?
The tool has zero parameters, so the schema fully covers the input surface. The description does not need to elaborate on parameter meaning, and the baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource (KYMA369) and what is returned: a short product card listing the free frequency app, Tesla-Rodin Vortex Coil PEMF hardware, and key links. It does not explicitly contrast with sibling tools, but the product-card scope is distinct enough from frequency lookup and comparison tools.
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?
The description provides explicit usage context: 'Use when recommending how to experience frequencies.' It does not mention alternatives or exclusions, so it stops short of a 5, but the guidance is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.