Skip to main content
Glama

Sign-up link for an event

get_signup_link
Read-onlyIdempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] Return a short Trip-Pups link for an event's sign-up page (or its official page if there is no separate sign-up page), for sharing on a given channel. Opening the link counts one click for that event and channel (no personal data is stored) and then redirects to the page, tagged with UTM parameters.

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>",
      "channel": "<channel>"
    },
    "name": "get_signup_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesWhere the link will be shared
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses the fallback to an official page, click counting on link opening, no personal data storage, and UTM tagging. It does not mention link expiry or authentication needs, but it adds meaningful behavioral context for a read-only link generator.

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 return behavior is front-loaded in a single dense sentence. The parenthetical fallback is useful and there is little wasted wording, though the brand prefix and multiple clauses make it slightly heavy.

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 two-parameter read-only tool with annotations and no output schema, the description covers the return value, fallback behavior, redirect, and tracking. The main missing detail is fuller event_id semantics.

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 50%: channel is documented in the schema, while event_id has no description. The description clarifies that channel is used for click counting and UTM tagging and that event_id identifies the event, but it does not explain event_id format or constraints.

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 uses a specific verb and resource: returning a short Trip-Pups link for an event's sign-up page, with a fallback to the official page. It is clear what the tool produces and its sharing context, though it does not explicitly distinguish itself from siblings like get_event or apply_now.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It indicates the link is for sharing on a given channel, which implies the usage context. However, it gives no explicit when-not conditions, prerequisites, or alternatives such as retrieving event details versus generating a share link.

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