Skip to main content
Glama

evite_open

Opens an Evite page in your signed-in Cloud Browser so you can manage hosted events, guest lists, RSVPs, messages, and reminders.

Instructions

Open a Evite page in your signed-in Cloud Browser (default https://evite.com) to work with manage hosted events, guest lists, RSVPs, messages and reminders.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 that the browser is "signed-in" (authentication is handled by the session) and supplies the default URL, which is real context. It does not say whether it navigates an existing tab or opens a new one, what happens on failure, or whether page content is returned or must be fetched via evite_read.

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?

One front-loaded sentence with the action verb first and no padding. It is appropriately sized for a simple navigation tool, with only the awkward grammar costing it the top score.

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 tool with no output schema, the essentials are present: what it opens, in what authenticated context, and the default target. What is missing is what the agent gets back and how it relates to the follow-up tools (evite_read, evite_status), which matters for chaining a browser workflow.

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 description coverage is 100% and the single optional parameter is fully documented there, so baseline is 3. The description's restatement of the default URL (https://evite.com) duplicates what the schema already says rather than adding new meaning such as accepted URL forms or restrictions.

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 gives a specific verb and resource ("Open a Evite page in your signed-in Cloud Browser") and scopes the use case to managing hosted events, guest lists, RSVPs, messages and reminders. It is distinguishable from siblings like evite_read or evite_click, though it never explicitly contrasts itself with them. Minor grammar issues ("a Evite", "to work with manage") slightly muddy the phrasing but not the intent.

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 implied: this is the navigation entry point that precedes interaction tools such as evite_click, evite_type and evite_read. However, the description never states when to use this versus those siblings, nor any exclusion or prerequisite sequencing. An agent must infer that opening a page is the first step.

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