Skip to main content
Glama
stdict-mcp-server

stdict-mcp-server

search_dictionary

Search Korean dictionary headwords and definitions using exact, partial, wildcard, or part-of-speech filters, with paginated results.

Instructions

국립국어원 표준국어대사전에서 표제어와 뜻풀이를 검색합니다.

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_dictionary"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo결과 개수
queryYes검색어
startNo검색 시작 번호
methodNo검색 방식exact
partOfSpeechNo품사 코드 목록. 0은 전체, 1 명사, 5 동사, 6 형용사

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only query against an external dictionary and discloses the source, but says nothing about rate limits, availability, result ordering, or what a wildcard search does; for a search tool with no annotations this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single short sentence with the source and search scope front-loaded and no filler. It is efficient, though the brevity leaves little structure to build on.

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 5 parameters, full schema coverage, and no output schema, the description is thin but the schema does the heavy lifting. Missing are the enum behavior for method (especially wildcard syntax) and pagination semantics, which an agent would need for non-default queries.

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 description coverage is 100%, so every parameter (query, count, start, method, partOfSpeech) is already documented in the schema. The description adds only that the search covers both headwords and definitions, which is mild scope information, not parameter-level semantics such as wildcard syntax or part-of-speech code details.

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 a specific resource (국립국어원 표준국어대사전의 표제어와 뜻풀이). This is clearly a search over the Standard Korean Dictionary and is distinguishable in kind from a single-entry lookup sibling, though the description never explicitly contrasts with it.

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?

Implicitly frames the tool as a lookup/search entry point, but gives no when-to-use guidance, no condition selecting it over get_dictionary_entry, and no guidance on which search method (exact/include/start/end/wildcard) to pick.

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