ntis-mcp

search_rnd_programs

Search Korean national R&D programs (사업) to obtain program ID, name, year, managing agency, ministry, and budget. Data sourced from ntis.go.kr.

Instructions

Search Korean national R&D programs (사업) — the umbrella programs under which individual projects are funded. Returns program ID, name, year, managing agency (전문기관), ministry, and budget when listed. Data source: ntis.go.kr.

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": {
      "query": "<query>"
    },
    "name": "search_rnd_programs"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`query`	Yes
`page_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It lists return fields and data source but does not disclose side effects, authentication needs, or rate limits. For a read-only search, safety is implied but not explicit.

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 sentences with clear structure: first states purpose and resource, second lists return fields and data source. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Reasonably complete for a simple search tool, covering purpose, output fields, and data source. However, missing parameter explanations and explicit usage guidance reduce completeness.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any parameters. It omits explanation of 'query', 'page', or 'page_size' beyond their schema names, failing to compensate for the gap.

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?

Clearly states it searches Korean national R&D programs, explains what a program is (umbrella for projects), lists return fields, and distinguishes from siblings by naming search_rnd_announcements and search_rnd_projects.

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?

Implicitly guides usage by differentiating from siblings (projects vs announcements), but lacks explicit when-to-use or when-not-to-use instructions.

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

Deploy Server