Skip to main content
Glama

Join a Trip-Pups day out (signs up for real)

join_meetup
Idempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] Sign the traveler up for a small-group day out hosted by Trip-Pups (events marked hosted_by: trippups). This completes the sign-up: it is recorded and the team sees it. Only call it after the traveler has given these details themselves and said yes in this conversation. Never guess or fill in a detail. Does not work for other organizers' events. Privacy notice: https://trip-pups.com/hi/weekly#privacy

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>",
      "name": "<name>",
      "contact": "<contact>",
      "country": "<country>",
      "school": "<school>",
      "age_confirmed": "<age_confirmed>",
      "consent": "<consent>"
    },
    "name": "join_meetup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe traveler's name
phoneNoOptional. Phone or WhatsApp from any country, with country code, e.g. +1 555 123 4567. No Korean number needed; leave it out if they'd rather not give one.
schoolYesTheir school, or how long they're in Korea
consentYesTrue only if the traveler agreed to the privacy notice
contactYesEmail or @Instagram, where the meeting details go
countryYesWhere they're from
event_idYesEvent id from search_events, starting with tp-weekly-
age_confirmedYesTrue only if the traveler confirmed they are 14 or older

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say it is a non-destructive, idempotent, open-world write. The description adds the material fact that this is a real, recorded commitment the team sees, that it completes sign-up, and that a consent plus age-14 confirmation gate the call — none of which is inferable from the annotations. It omits what a repeat or failed submission looks like, which matters for an idempotent write.

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?

Purpose and organizer scope come first, then the consent precondition, then the privacy link — a sensible priority order with no filler sentences. The bracketed bilingual header is noisy but very brief.

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 an 8-parameter, 7-required write with no output schema, the definition covers the essential context: real-world effect, who must consent, age requirement, and privacy disclosure. It leaves unstated what the agent should expect on success or on a duplicate submission, which is the main remaining gap.

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%, so parameter meaning is already carried by the schema (name, contact, country, school, consent, age_confirmed, event_id). The description reinforces the behavioral rule that no value may be invented or inferred, but contributes no field-level detail such as contact format or event_id source beyond what the schema already states.

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?

States a specific verb and resource — 'Sign the traveler up for a small-group day out hosted by Trip-Pups' — and narrows scope with 'events marked hosted_by: trippups' plus 'Does not work for other organizers' events,' so the agent can separate it from apply_now or get_signup_link without opening the schema.

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?

Gives a hard precondition ('Only call it after the traveler has given these details themselves and said yes in this conversation. Never guess or fill in a detail') and a clear exclusion (other organizers' events). It stops short of naming which sibling to route to when the event isn't Trip-Pups, but the when/when-not boundary itself is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources