Skip to main content
Glama
Sign In
WaveXisMCP

WaveXisMCP

by MathiasPaulenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

wavexis_reload

Reload the current browser page, with an option to bypass cache, to refresh stale content or retry a failed load.

Instructions

Reload the current page, optionally bypassing the cache.

Use to refresh stale content or retry a failed load; use wavexis_navigate to go to a different URL instead.

Side effects: Re-issues network requests for the current page and its resources; discards in-memory page state. Returns: JSON string with keys: 'status' ('ok'/'error').

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": {
      "input": "<input>"
    },
    "name": "wavexis_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.24
    • addedInput schema / $defs / ReloadInput / properties / session_id / description
      Added value: +"Active session ID from wavexis_session_open"
  2. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Discloses side effects: re-issues network requests and discards in-memory page state. Annotations provide no hints, so description adds value. Could mention if it's safe but not required.

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?

Three sentences, front-loaded, no wasted words. Purpose, usage, side effects, and return value are all covered efficiently.

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 simple reload tool with two parameters and known output format, the description is complete. Side effects and return type are specified.

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 descriptions cover both parameters; description adds minimal extra meaning ('optionally bypassing the cache' for ignore_cache). Baseline 3 as schema coverage is high in the schema itself.

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 'Reload the current page' with a specific verb and resource, and distinguishes from wavexis_navigate for going to a different URL.

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

Usage Guidelines5/5

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

Explicitly says when to use (refresh stale content, retry failed load) and when not (use wavexis_navigate), with clear side effects.

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