Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Get Service Status

get_service_status
Read-onlyIdempotent

Shows which Korean public API keys are configured and lists available tools per service; check it first when another tool returns an API key error.

Instructions

어떤 서비스의 API 키가 설정됐는지(값은 숨김)와 서비스별 사용 가능한 도구를 보여줍니다. 도구가 키 오류를 낼 때 먼저 확인하세요.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds behavior those annotations do not: secret values are hidden in the output, and the result enumerates both configured keys and the tools available per service. Rate limits or failure modes are not mentioned, but they are not especially relevant for a zero-parameter local status check.

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 short sentences: the first defines the output, the second front-loads the usage trigger. No filler, no repetition of the title, and the masked-values caveat is folded in economically.

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 an output schema present, the description does not need to enumerate return fields, and it covers purpose, secret masking, and the error-diagnosis entry point. The only minor gap is what an empty or partially configured result implies for the agent's next step.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4 and there is nothing further the description could usefully disambiguate. It correctly implies the call is global across services rather than scoped to one.

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 states a specific verb-and-resource pair: it reports which services have API keys configured (with values masked) and which tools are available per service. That is clearly distinct from the data-fetching siblings listed, though it never names or contrasts any of them explicitly.

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 a concrete trigger condition: call this first when another tool reports a key error. It provides no negative guidance (e.g., when this check is unnecessary) or alternatives, but the primary entry condition is stated plainly.

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