Skip to main content
Glama
stdict-mcp-server

stdict-mcp-server

get_dictionary_entry

Retrieves detailed Korean dictionary entries by headword or targetCode, including definitions, part of speech, and usage examples.

Instructions

표제어나 검색 결과의 targetCode로 상세 뜻풀이, 품사, 용례를 조회합니다.

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

Input Schema

NameRequiredDescriptionDefault
queryYes표제어나 검색 결과의 targetCode
lookupByNo표제어 또는 targetCode로 조회word

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; '조회' clearly signals a non-mutating read, and it discloses what content comes back (definition, part of speech, examples). It says nothing about failure modes such as an unknown targetCode, lookup limits, or authentication requirements.

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?

A single front-loaded sentence that names the two input modes first and the three returned artifacts second, with no filler. Every clause carries information an agent needs.

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 read tool with full schema coverage and no output schema, the description covers input modes and return content sufficiently. Only the relationship to search_dictionary and behavior on a bad code remain unaddressed.

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 both query and lookupBy are already documented in the schema, establishing a baseline of 3. The description restates the two lookup modes without adding format guidance (e.g., where targetCode is found in a search response) beyond 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 uses a specific verb (조회) with a named resource (표제어/사전 뜻풀이) and enumerates the returned fields (뜻풀이, 품사, 용례). It implicitly distinguishes itself from search_dictionary by referencing '검색 결과의 targetCode', but never names the sibling outright.

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 implied rather than stated: '검색 결과의 targetCode' suggests this is the second step after a search, which an agent can infer. There is no explicit when-to-use/when-not or a named alternative to route to, leaving the sequencing to inference.

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