Skip to main content
Glama
Sign In
ASX Options Game MCP

ASX Options Game MCP

by rknell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

game_navigate

Open a specific TradeFloor game view and return a structured snapshot for reviewing home, portfolio, performance, strategy, or orders; switching views may discard an unsubmitted form.

Instructions

Open a game view and return a snapshot. May discard an unsubmitted form. Account-specific URLs are discovered from the logged-in page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "view": "<view>"
    },
    "name": "game_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well by disclosing two important traits: it may discard an unsubmitted form, and account-specific URLs come from the logged-in page. It still does not describe the returned snapshot format or any permission requirements.

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 three tight sentences, front-loads the main purpose, and each sentence adds distinct value: purpose, side-effect warning, and authentication context.

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

Completeness3/5

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

For a one-parameter navigation tool with no output schema, the description covers purpose, side effects, and login context. It is still missing the meaning of the view options and does not explain what the returned snapshot contains.

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

Parameters2/5

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

The schema has 0% description coverage, and the description does not explain the 'view' parameter or the meaning of the enum values (home, portfolio, performance, strategy, orders). The schema alone lists valid values, so the description adds essentially no parameter semantics.

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 verb and resource: 'Open a game view and return a snapshot.' It is clear what the tool does, but it does not explicitly differentiate itself from sibling game_snapshot, which also involves snapshots.

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

Usage Guidelines3/5

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

It implies usage by saying the tool opens a game view, and the warning about discarding an unsubmitted form gives a useful caution. However, it does not say when to prefer game_snapshot or game_screenshot, nor does it state explicit alternatives.

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