Skip to main content
Glama

whova_open

Opens a Whova page in your signed-in Cloud Browser so you can manage event agendas, attendees, registrations, announcements, speaker messages, and post-event reports.

Instructions

Open a Whova page in your signed-in Cloud Browser (default https://whova.com) to work with manage event agendas, attendees, registrations, announcements, speaker messages and post-event reports.

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": "whova_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://whova.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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 burden, and it does disclose a genuine behavioral fact: the page opens inside a signed-in Cloud Browser session (auth context) with whova.com as the default target. It does not say whether the call waits for load, whether it returns page content or just navigates, or what happens on an invalid/unreachable URL — meaningful gaps for a navigation tool. Adds real value, but not enough for a mutation-free, annotation-less tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one sentence and front-loads the verb, which is good, but it crams the default URL and a six-item list of work domains into the same clause, producing the awkward 'work with manage'. The enumeration does earn some of its space by clarifying purpose, yet the sentence would read better split or trimmed.

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-optional-parameter navigation tool with no annotations and no output schema, the definition covers auth context and target URL. However, it is silent on what the call yields (page content? just a handle? a screenshot?), which matters because a sibling named whova_read exists for reading — an agent cannot tell whether open also returns content. Complete enough to call, not complete enough to call confidently.

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% and the single parameter already documents 'Page to open. Default: https://whova.com'. The description merely restates the same default host, adding no format, path, or validation detail beyond the schema. Baseline 3 is appropriate when the schema does all the work.

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?

States a specific verb and resource: 'Open a Whova page in your signed-in Cloud Browser', and enumerates the work domains (agendas, attendees, registrations, announcements, messages, reports) that the opened page enables. This distinguishes it from siblings like whova_read and whova_click, which operate on an already-open page. Minor deduction for the garbled phrase 'to work with manage event agendas', which muddies an otherwise clear purpose.

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?

Usage is only implied: the tool opens a page so you can then 'work with' event data, which suggests it precedes reading/clicking actions. It never explicitly says when to use this versus whova_read or whova_guide, nor any exclusions or prerequisites beyond the 'signed-in' hint. Adequate but leaves the agent to infer sequencing.

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