Skip to main content
Glama
Sign In
ygopro-mcp

ygopro-mcp

by darknessWONG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

control_start

Starts the Yu-Gi-Oh! duel as host when both players are ready by clicking Start in the YGOPro client.

Instructions

Click "Start" (CTOS_HS_START). Only valid when we are the host (seat 0) and both players are ready.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "control_start"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the host-seat and readiness gating conditions, but does not explain side effects, failure behavior, or what happens to the lobby/game state after the click.

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 short sentences with the action front-loaded and the validity condition immediately following. There is no redundant or filler text.

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?

For a simple zero-parameter game-control action, the description covers the action and its key precondition. It could be richer about post-action effects or sibling routing, but it is largely complete for the tool's complexity.

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 there is no parameter semantics to add beyond the schema. The baseline for a parameterless tool 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 states a specific action: clicking Start, with the internal code CTOS_HS_START. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as control_ready or control_lobby.

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?

It gives a clear precondition: only valid when the caller is host (seat 0) and both players are ready. It does not state what to do when those conditions fail or which sibling tool should be used instead, so it stops short of full when/when-not guidance.

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

Deploy Server

Other Tools