Skip to main content
Glama

Wavedash

by io.github.wvdsh

Get Wavedash Quickstart

wavedash_get_quickstart
Read-only

Return the Wavedash setup path for a browser game, optionally including an engine and SDK features. Read-only and unauthenticated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineNoOptional engine/framework, for example phaser, unity, godot, three.js, react, rust, or custom.
featuresNoOptional Wavedash features, for example multiplayer, achievements, leaderboards, cloud-saves, ugc, players.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesHuman-readable tool result text.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'unauthenticated' which is a new behavioral trait beyond annotations. No contradiction. However, it does not disclose any other behaviors (e.g., what happens when engine is invalid).

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 concise sentences, front-loaded with purpose, and no wasted words. Every sentence serves a purpose.

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 simplicity of the tool, no required parameters, and an existing output schema, the description is mostly complete. It could mention that the returned path is a URL or structured object, but 'setup path' is sufficient.

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 coverage is 100%, so the schema already describes both parameters (engine, features) with descriptions. The description mentions 'optionally including an engine and SDK features' but adds no additional meaning or constraints beyond the schema.

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 states a specific verb and resource ('Return the Wavedash setup path') and distinguishes from sibling tools by focusing on 'quickstart' and 'setup path' for browser games.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like wavedash_get_doc or wavedash_get_sdk_reference. Only states it is read-only and unauthenticated, but no context on prerequisites or exclusions.

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