Skip to main content
Glama
chrischall

vibo-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vibo_join_event

Join an event by entering its shared link or hash, returning the event ID after user confirmation.

Instructions

Join an event you were invited to, via its share link or hash (e.g. a vibodj.app.link/... URL someone sent you). Returns the joined event's id. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkYesThe full event share URL (vibodj.app.link/... or web.vibodj.com/...) or the bare join hash.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.5.1
  4. Removedv1.4.3
  5. First observedv1.3.1

TDQS

A4.3/5.0
Behavior5/5

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

The description goes well beyond what annotations provide, fully disclosing the confirmation requirement and the two-step fallback flow: first call returns a preview and confirmToken, and only a repeat call with that token proceeds. It also states the return value (joined event's id). This is critical, non-obvious behavioral context that the readOnlyHint=false / destructiveHint=false annotations do not convey, and it does not contradict them.

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?

Three sentences, each earning its place: the action, the return value, and the confirmation protocol. The purpose is front-loaded. The middle sentence is dense, packing both the prompt-supported path and the fallback path, but the complexity of the two-step flow justifies the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter tool with 100% schema coverage, the description is nearly complete: it covers the action, the input format, the return value, and both confirmation modes, with a pointer to MCP_CONFIRM_MODE. Minor gaps remain, such as behavior on invalid/expired links or joining an event the user already belongs to, but these are edge cases rather than invocation-blocking omissions.

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%: both `link` and `confirmToken` already carry detailed descriptions, including URL/hash formats and the strict rules on confirmToken (never on first call, never invented, never reused). The main description adds little beyond the schema—it references the share-link mechanism but introduces no new parameter meaning—so the baseline 3 applies.

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 states a specific verb ('Join'), resource ('event'), and method ('via its share link or hash'), which clearly distinguishes it from sibling tools like vibo_get_event, vibo_list_events, and vibo_leave_event. Citing the example URL format (vibodj.app.link/...) makes the action concrete and unambiguous.

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 'an event you were invited to' plus the mention of a share link establishes clear context for when the tool applies. However, it does not explicitly name alternatives or state when NOT to use it (e.g., to browse events use vibo_list_events, to view an event you already belong to use vibo_get_event).

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