Skip to main content
Glama
Sign In
contest-mcp

contest-mcp

by mytrashcan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_contest

Retrieves detailed information for a single Korean contest—eligibility, prizes, scoring, submission requirements, announcements, and contact—with source evidence, optionally refreshing cached data.

Instructions

공모전 1건의 상세(자격·시상·배점·제출물·발표·문의처)를 원문 근거와 함께 가져온다.

Args: ident: wevity:112073 같은 id, 상세 URL, 또는 ix·contest_pk 값. refresh_detail: True면 상세 페이지를 지금 받아 갱신(하루 1회 캐시).

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": {
      "ident": "<ident>"
    },
    "name": "get_contest"
  }
}

Input Schema

NameRequiredDescriptionDefault
identYes
refresh_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose non-obvious behavior: results are cached at one fetch per day and refresh_detail=True forces a live re-fetch, and responses are returned with original-source evidence. It does not cover failure behavior for an invalid identifier, 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 tight components: a front-loaded purpose sentence that lists the returned content, then a compact Args block covering both parameters. No filler, no restating the tool name, and the highest-value details (identifier formats, cache rule) are surfaced immediately.

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?

No output schema exists, so the description must convey the return shape, and it does by enumerating the detail sections and noting source citations accompany them. For a two-parameter read tool this is nearly complete; only edge behavior on unresolvable identifiers is unaddressed.

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 coverage is 0% – the schema exposes only bare titles ('Ident', 'Refresh Detail') – so the description is doing all the work, and it does: it gives three concrete accepted identifier forms (wevity:112073 style id, detail URL, or ix/contest_pk) and explains exactly what refresh_detail toggles and its cache implication. This is meaning the agent could not obtain from 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?

States a specific verb and resource: fetch the details of a single contest, with an enumerated field list (eligibility, prizes, scoring, submissions, announcements, contact) plus source grounding. This clearly separates it from a list/search tool, but it never names a sibling such as search_contests or check_eligibility, so differentiation is inferred rather than stated.

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?

Usage is only implied: the single-item scope and the 'fetch now vs. use daily cache' toggle suggest it is the follow-up call after search, but there is no explicit when-to-use, when-not-to-use, or named alternative. The refresh_detail note gives partial operational guidance without framing it as a decision rule.

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

Deploy Server

Other Tools