Skip to main content
Glama

Trip-Pups meetups you can join

list_meetups
Read-onlyIdempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] List the small-group days out that Trip-Pups itself runs in Seoul for international students and travelers, from today on: when, where, cost, seats left and sign-up deadline, read live from our sign-up list. No dates needed. Every open one can be joined right in this chat with join_meetup. No Korean phone number is needed to join.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description contributes genuinely new behavioural context: results are read live from the sign-up list (freshness), the window starts today (no past entries), and no Korean phone number is required to join. It stops short of describing ordering or result limits.

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?

Effectively one dense sentence with scope, fields, freshness and the follow-up tool all front-loaded; nothing is filler. The bracketed Korean name/tagline at the start is brand noise that slightly delays the substance.

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

Completeness5/5

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

For a zero-parameter read tool with full annotation coverage, this covers everything an agent needs: what is returned, the time window, data provenance, and the natural next action. No output schema exists, and the description compensates by listing the returned fields inline.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters and 100% schema coverage, so baseline is high. The description reinforces this with 'No dates needed', pre-empting the most likely agent assumption that a date filter must be supplied.

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 (list) and a precisely scoped resource: the small-group days out that Trip-Pups itself runs in Seoul for international students and travelers, starting from today. The 'Trip-Pups itself runs' qualifier implicitly separates it from the broader search_events sibling, and the enumerated return fields (when, where, cost, seats left, sign-up deadline) make the output shape 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?

Gives clear context for use — browsing upcoming joinable meetups without needing dates — and explicitly routes the follow-up action: 'Every open one can be joined right in this chat with join_meetup.' It does not state exclusions, e.g. when to prefer search_events for non-Trip-Pups events, so guidance is strong but not fully two-sided.

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