Skip to main content
Glama

everyone-builder

free_courses

지금 수강 신청할 수 있는 무료·국비 지원 온라인 강좌를 마감일 순으로 돌려줍니다 (K-MOOC 등 공공 API, 1,800여 개 중 모집 중인 것). 날짜는 모집 마감일이며 개강일과 다릅니다. query 로 주제를 좁힐 수 있습니다 (예: '파이썬', '데이터 분석').

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

Input Schema

NameRequiredDescriptionDefault
limitNo돌려받을 개수 (1~30, 기본 15). 넘기면 30에서 잘립니다
queryNo찾을 주제. 비우면 마감 임박순

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 burden and does substantial work: it names the data source (K-MOOC and other public APIs), the approximate corpus and that only actively recruiting items are returned, and it flags the non-obvious fact that the returned date is the application deadline, not the course start date. It omits permission/auth requirements and rate limits, but for a read-only listing tool 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.

Conciseness5/5

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

Three short sentences: what it returns and ordering first, then the critical date-semantics caveat, then the filtering hint. Every sentence carries distinct information and the bold emphasis lands on the one genuinely surprising detail.

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, zero-required read tool with no output schema and no annotations, the description covers purpose, ordering, source, scope, and the ambiguous date field. What is left unstated — the shape of each returned course record and whether results are truncated at 30 — is partly covered by the schema's limit description.

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%, so both limit and query are already documented in the schema, including the default, max, and truncation behavior. The description adds only the illustrative topic examples for query, which is marginally useful but largely redundant with '찾을 주제' in the schema.

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 gives a specific verb and resource ('무료·국비 지원 온라인 강좌를 ... 돌려줍니다') plus a scope qualifier ('지금 수강 신청할 수 있는', sorted by deadline). It does not name or differentiate against any sibling, though none of the listed siblings (draft_post, korea_it_news, open_competitions) is obviously confusable except perhaps open_competitions.

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 clearly sets the usage context — only courses currently open for enrollment — and explains how to narrow results via the query parameter with concrete topic examples. It stops short of stating exclusions or naming an alternative tool for related needs (e.g., competitions vs. courses).

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