Skip to main content
Glama

evite_guide

Call this guide first for using Evite to manage hosted events, guest lists, RSVPs, messages, reminders, and sign-in.

Instructions

How to work in Evite (manage hosted events, guest lists, RSVPs, messages and reminders): 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": "evite_guide"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies an informational guide but does not confirm that it is read-only, does not describe what it returns (e.g., instructions or links), and does not state whether it has side effects.

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 two compact sentences with no wasted wording. The scope is front-loaded and the critical instruction to call it first is easy to find.

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 low-complexity guide tool with no output schema, the description covers the intended domain and ordering guidance. However, it does not explain the return behavior or clarify that calling it is informational rather than action-performing, leaving an important gap for an agent.

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 one parameter, 'task', and schema description coverage is 100%, so the schema already explains that it accepts a plain-language task description. The tool description adds no additional meaning about how to phrase or use that parameter.

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 clearly identifies this as a guide for working in Evite, covering screens, sign-in link, hosted events, guest lists, RSVPs, messages, and reminders. It distinguishes itself functionally from siblings like evite_click or evite_type by being an introductory how-to, though it does not explicitly name those alternatives.

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?

The phrase 'Call this first' gives explicit ordering guidance before using other Evite tools. It also lists relevant domains of use. It does not state when not to use it or name specific alternatives, which keeps it below a 5.

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