Skip to main content
Glama

everyone-builder

open_competitions

마감 전인 AI·개발 대회와 해커톤을 마감일·상금과 함께 돌려줍니다 (Kaggle · Devpost · K-Startup 등 공개 API). 국내 해커톤은 모아 주는 공개 API 가 없어 수집하지 못하므로, 대신 국내 해커톤·공모전을 모아 둔 사이트 12곳을 함께 안내합니다.

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

Input Schema

NameRequiredDescriptionDefault
limitNo돌려받을 개수 (1~30, 기본 15). 넘기면 30에서 잘립니다

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the data provenance, the deadline filter, and the important negative behavior (no domestic hackathon collection, replaced by a curated list of 12 sites). It omits freshness/refresh cadence and rate-limit or auth details, which keeps it short of a 5.

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?

Two tightly written sentences: the first front-loads what is returned and from where, the second handles the coverage gap and the substitute behavior. No filler and no redundancy.

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?

With no output schema, the description must convey what comes back, and it does: competitions with deadlines and prizes plus a list of 12 Korean aggregator sites. The exact response shape (whether the site list is a separate field or inline text) is left implicit, which is a minor gap for a no-output-schema tool.

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?

The single limit parameter is fully described in the schema (1–30, default 15, clamped at 30), so the schema does the heavy lifting here. The description adds no additional meaning about the limit or its interaction with the appended site list.

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 names a specific verb and resource — it returns AI/development competitions and hackathons before their deadline, along with deadline and prize — and lists the upstream sources (Kaggle, Devpost, K-Startup). This is distinguishable at a glance from siblings such as free_courses or korea_it_news.

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?

It gives clear scope and an explicit limitation: Korean hackathons are not collected because no public aggregating API exists, and instead 12 Korean contest-aggregator sites are pointed to. There is no explicit when-to-use-versus-alternative routing, but the stated data coverage makes the appropriate use case unambiguous.

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