Skip to main content
Glama

whova_guide

Guides you through Whova organizer screens and the sign-in link so you can manage agendas, attendees, registrations, announcements, speaker messages, and post-event reports. Call it first.

Instructions

How to work in Whova (manage event agendas, attendees, registrations, announcements, speaker messages and post-event reports): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Whova, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, but the description makes the informational nature reasonably apparent through 'How to work in Whova' and the enumeration of domains it explains. It does not state whether calling it merely returns orientation text or also establishes session/auth state, nor how the response is shaped. For a zero-annotation tool this leaves some behavioral burden unaddressed.

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

Conciseness4/5

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

A single compact sentence with no filler. The long parenthetical sits in the middle while the most actionable instruction, 'Call this first', is buried at the end rather than front-loaded, which slightly weakens structure.

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 guide tool with no output schema, the description covers what domains it explains and that it should be used first. It is less clear on what the caller receives back and whether the sign-in link implies an authentication prerequisite, which an agent needs to sequence correctly.

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?

There is a single optional 'task' parameter with 100% schema description coverage ('What you want done in Whova, in your words'), so the schema already carries its meaning. The description's list of domains implicitly scopes what a task can be, but adds no format, sizing, or example guidance beyond the schema. Baseline 3 applies given high coverage.

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 recognizable purpose: orienting the agent in Whova, covering screens and the sign-in link, and enumerating the operational domains (agendas, attendees, registrations, announcements, speaker messages, reports). It distinguishes itself from the action siblings (whova_click, whova_read, etc.) by being the orientation entry point. The phrase 'its screens and the sign-in link' is slightly vague about what is actually returned.

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?

'Call this first' is an explicit, unambiguous sequencing directive, which is exactly the guidance an agent needs for a guide/orientation tool. It does not state when the tool becomes unnecessary or how it relates to the sibling action tools after the first call, so it stops short of full when/when-not coverage.

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