Skip to main content
Glama

Apply now (walk-in guide, form preview, or hand-off)

apply_now

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] One step toward joining an event, chosen by how the event takes sign-ups (signup_type). walk_in: tells the traveler no advance sign-up is needed and how to get there (nothing is recorded). web_form: mode=preview (default) shows exactly which fields of the organizer's form would be filled with the traveler's details; nothing is sent to the organizer and nothing is stored. naver_booking / phone_verify / paid_ticket / unknown: cannot be completed automatically. In mode=preview this tool only explains what a hand-off to a Trip-Pups team member would involve and stores nothing; to actually hand the request over, call request_application_help after the traveler agrees. In mode=preview apply_now never stores or sends anything, whatever the sign-up method. mode=submit is turned off on this server unless the operator enables it. consent must be true, meaning the traveler agreed to share these details for this sign-up. 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>",
      "applicant": "<applicant>",
      "consent": "<consent>"
    },
    "name": "apply_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language: en (default) or koen
modeNopreview
consentYesMust be true: the traveler agreed to share these details for this sign-up
event_idYesEvent id from search_events
applicantYesThe traveler's details, exactly as they gave them
submit_consentNomode=submit only: true means the traveler read the organizer's form and consent text and agrees that we send it for them, in their own name and details

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing what is and is not persisted per mode, that submit mode is off by default on this server, that consent must be true, and by linking the privacy notice. These are exactly the operational facts an agent needs before invoking something that looks like a write.

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?

The core idea and the signup_type branch table are front-loaded, and the per-method breakdown is easy to scan. The main cost is redundancy: the guarantee that nothing is stored is asserted three separate times ('nothing is sent... nothing is stored', 'stores nothing', 'never stores or sends anything'), which could be collapsed.

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 6-parameter tool with a nested applicant object and no output schema, the definition covers the branching logic, the safety story, and the escalation path to request_application_help. The only gap is that it never says what the traveler receives back in each mode, which is minor because no output schema is declared and the behavior is described narratively.

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?

Schema coverage is already 83%, yet the description still adds real meaning: it explains that mode=preview is the default and what it does, that consent means the traveler agreed to share these details, and that submit_consent applies only to mode=submit. It does not explain the lang parameter or the applicant.date field beyond the schema, so it is additive rather than complete.

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 names a specific action (complete/advance one sign-up step) and immediately scopes it by signup_type, enumerating walk_in, web_form, naver_booking, phone_verify, paid_ticket and unknown outcomes. It is distinguishable from request_application_help, but the verb itself ('apply_now' that mostly previews and never applies) is only resolved after careful reading of a dense paragraph.

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?

Explicit routing is given for the non-automatable methods: 'to actually hand the request over, call request_application_help after the traveler agrees', plus the precondition that mode=submit is disabled unless the operator enables it. It does not tell the agent when to prefer the sibling get_walk_guide for the walk_in case, and it never states a prerequisite like 'call get_event first', so guidance is strong but not exhaustive.

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