Skip to main content
Glama

Wavedash

by io.github.wvdsh

Get Wavedash SDK Reference

wavedash_get_sdk_reference
Read-only

Fetch Wavedash SDK docs for a specific feature such as setup, multiplayer, achievements, leaderboards, cloud saves, UGC, players, events, or types. Read-only and unauthenticated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesSDK topic, for example setup, multiplayer, lobbies, p2p, achievements, stats, leaderboards, cloud-saves, ugc, players, cli, config.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesHuman-readable tool result text.

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint, and the description adds 'unauthenticated', which is not in annotations. No contradictions. This extra behavioral detail helps the agent assess prerequisites.

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?

Two sentences, no waste. First sentence states purpose with examples, second adds behavioral constraints. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with full schema coverage and an output schema, the description provides all necessary context. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the 'topic' parameter, which already lists examples. The description repeats those examples but adds no deeper semantic meaning, so it meets the baseline for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Fetch' and resource 'Wavedash SDK docs', with specific examples of topics. It distinguishes from siblings like wavedash_get_doc and wavedash_search_docs by focusing on SDK reference.

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 notes the tool is 'Read-only and unauthenticated', which provides clear context for safe usage. It does not explicitly contrast with alternatives, but the listed examples and sibling names imply its specific scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wavedash toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: workflow, documentation retrieval, checklists, quickstart, SDK reference, planning, search, and config validation. No overlap.

Naming Consistency4/5

Most tools follow verb_noun pattern with 'get_' prefix, but 'implementation_planner' deviates as a noun phrase, slightly reducing consistency.

Tool Count5/5

8 tools is well-scoped for a documentation and planning assistant—not too few to cover needs, not too many to overwhelm.

Completeness5/5

The tool set comprehensively covers the stated domain: fetching docs, planning implementations, searching, and validating config. No obvious gaps for its read-only purpose.

Resources