Skip to main content
Glama
korea-data-mcp

korea-data-mcp

by parkseokjune

wadiz_campaigns

Fetch Wadiz reward-crowdfunding campaigns with title, maker, category, funding amount, rate, status, and URL. Filter by live or ended and order by popularity, recency, or ending soon.

Instructions

Return reward-crowdfunding campaigns from Wadiz, Korea's largest crowdfunding platform: title, maker, category, amount raised (KRW), funding rate, status, URL.

Args: mode: "feed" for live campaigns or "ended" for finished ones. order: "recommend", "popular", "recent" or "endsoon". maxItems: Maximum number of campaigns to return (billed per campaign).

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

Input Schema

NameRequiredDescriptionDefault
modeNofeed
orderNopopular
maxItemsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the most consequential trait an agent needs: "billed per campaign," which makes maxItems a cost lever. It also implies a read-only operation and lists returned fields, but says nothing about pagination, rate limits, auth requirements, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and returned fields, then a compact Args block with one line per parameter. No filler sentences; every clause either identifies the resource or constrains a parameter. The field list is mildly redundant with the output schema but is short and aids scanning.

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 three-parameter read tool with an output schema and no annotations, the definition covers what is needed to call it correctly: source, modes, orderings, result cap, cost, and return fields. Missing only operational detail such as whether maxItems has an upper bound or how results are paged.

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

Parameters5/5

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

Schema description coverage is 0% and there are no enums in the schema, so the description is the only source of valid values — and it supplies them fully: mode ("feed"/"ended"), order ("recommend"/"popular"/"recent"/"endsoon"), and maxItems as a count with a billing consequence. This is exactly the compensation a 0%-coverage schema requires.

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 ("Return reward-crowdfunding campaigns from Wadiz") and names the source platform, which distinguishes it from every sibling (danawa, kream, kurly, etc.). It even enumerates the returned fields, so an agent knows exactly what data comes back without opening the output 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?

Gives clear contextual guidance for two of the three parameters: "feed" for live campaigns vs "ended" for finished ones, plus the four ordering modes. It does not state exclusions or point to alternatives (e.g., other Korean commerce sources), but for a single-source listing tool the mode/order guidance covers the main selection decision.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.