Skip to main content
Glama

Ask Trip-Pups to help with sign-up

request_application_help

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] Ask the Trip-Pups team (real people) to help the traveler sign up for an event, e.g. when the official page is Korean-only or needs a Korean phone number. This does NOT sign up or book anything by itself: the request is stored, the team is notified, and a team member emails the traveler within 24-48 hours. Returns a reference number for check_application_status. Requires the traveler's agreement to share their name and email. Our 1:1 sign-up help is free. We only use your own name and details. We never complete identity or phone verification for you or with our accounts. Some organizers do not allow anyone else to sign up on your behalf; for those events we only guide you through doing it yourself. Name, email, party size and note are stored for up to 90 days; privacy notice: https://trip-pups-mcp.tree8727.workers.dev/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>",
      "email": "<email>",
      "party_size": "<party_size>"
    },
    "name": "request_application_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
noteNo
emailYes
event_idYes
party_sizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, non-destructive), the description discloses the full asynchronous lifecycle: the request is stored, the team is notified, a human emails within 24-48 hours, and a reference number is returned. It also states consent requirements, that the service is free, that identity and phone verification are never performed on the user's behalf, and the 90-day retention window with a privacy URL — unusually rich disclosure for a write-path tool.

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?

Purpose and the key non-guarantee are front-loaded, and most sentences carry distinct policy or process information. It is on the long side and the branding/locale header plus the repeated "your own details / never do verification for you" assurances overlap somewhat, but nothing is truly wasted.

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 five-parameter, non-idempotent request-creation tool with no output schema, the description supplies what an agent actually needs: what happens after the call, expected turnaround, what is returned (a reference number for check_application_status), and the consent and privacy constraints. The only real gap, the meaning of event_id, is minor relative to everything else covered.

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 0%, so the description must carry parameter meaning. It clarifies that name and email are the traveler's own details shared with consent and retained 90 days, and mentions party size and note — but event_id is never explained (presumably from search_events/get_event) and note's purpose (message to the team?) is undefined, leaving the two most agent-ambiguous fields to inference.

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 opens with a specific verb-and-resource framing ("Ask the Trip-Pups team to help the traveler sign up for an event") and immediately contrasts it with what it is not: "This does NOT sign up or book anything by itself." That negative clause is what separates it from sibling tools like apply_now or get_signup_link, so an agent can pick correctly without opening either 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?

Trigger conditions are concrete: use it when "the official page is Korean-only or needs a Korean phone number." A when-not case is also given: organizers who forbid third-party sign-ups get guidance only. What is missing is naming of the sibling alternatives (apply_now, get_signup_link, check_application_status as the follow-up path is named, but the primary self-serve alternative is not), so the routing is implied rather than explicit.

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