Skip to main content
Glama

Wavedash

by io.github.wvdsh

Get Wavedash Agent Workflow

wavedash_get_agent_workflow
Read-only

Return a concise end-to-end workflow for AI agents creating a browser game from scratch and preparing it for Wavedash upload. Read-only and unauthenticated; upload still happens through the Wavedash CLI or Developer Portal.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesHuman-readable tool result text.

TDQS

A4.5/5.0
Behavior5/5

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

The description confirms the read-only and unauthenticated nature, reinforcing the annotations. It also clarifies the upload process is separate, adding behavioral context beyond annotations without contradiction.

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 cover purpose and behavioral notes with no filler, achieving high conciseness while maintaining clarity.

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?

Given the low complexity (2 optional parameters, output schema exists), the description fully equips an agent to understand what the tool does, its constraints, and how it relates to the larger workflow.

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%, and the tool description repeats the parameter descriptions from the schema without adding new semantic information, meeting the baseline.

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 tool returns a concise end-to-end workflow for AI agents creating a browser game and preparing for Wavedash upload. It uses specific verbs and resource, and differentiates from sibling tools like wavedash_get_doc or wavedash_get_publishing_checklist.

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 that the tool is read-only and unauthenticated, and that upload happens via the CLI or Developer Portal, providing clear usage context. However, it does not explicitly state when to use this tool versus alternatives.

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