Skip to main content
Glama

Check a sign-up help request

check_application_status
Read-onlyIdempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] Check the status of a request made with request_application_help. Needs the reference number AND the same email that was given with the request; without a match nothing is shown.

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": {
      "reference": "<reference>",
      "email": "<email>"
    },
    "name": "check_application_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe email given when the request was made
referenceYesReference number, e.g. tp-abcd234xyz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive lookup, so the safety profile is covered. The description adds genuinely new behavior: both credentials must match and a mismatch silently returns nothing rather than an error. It doesn't describe what status values can come back, but absent an output schema that is a minor gap.

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?

Two sentences, front-loaded with purpose then credential requirement and failure mode; nothing redundant. The leading service branding and Korean marketing tag are minor noise that doesn't aid tool selection.

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 two-parameter read-only lookup with full schema coverage and complete annotations, the description supplies everything needed to call it correctly, including the silent-empty-result behavior. Only the possible status values are left unspecified.

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 100% and both properties are already documented, including an example reference format. The description reinforces the matching relationship between email and the original request, which is slightly more than the schema says, but adds no format or constraint detail beyond it.

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 (check the status of a help request) and explicitly ties it to the sibling that creates such requests, request_application_help. An agent can distinguish it from get_signup_link or get_event without opening any 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?

The description makes the use case conditional and explicit: only call it for a request previously made with request_application_help, and only when you hold both the reference number and the matching email. It doesn't spell out what to do when the request was never made or when an alternative lookup should be used, so it stops short of full when/when-not guidance.

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