Skip to main content
Glama

내만집 (nmjib) — Korean semi-self interior renovation

FAQ 검색

nmjib_faq_search
Read-onlyIdempotent

내만집 공개 문서에 실린 질문·답(FAQ) 수백 쌍에서 질문과 가장 가까운 것을 찾는다. 짧고 직접적인 답이 필요할 때 search 대신 쓴다. 각 답에 출처 URL 이 붙는다.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes질문(한국어)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful facts beyond them: the corpus is a bounded set of published FAQ pairs and each answer carries a source URL (valuable since there is no output schema). It says nothing about result ordering, empty-result behavior, or whether 'limit' truncates matches.

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?

Three short sentences, front-loaded with the resource and scope, then the alternative, then the return-value note. Every sentence carries distinct information with no repetition of the title or schema.

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-only lookup with no output schema, the description covers purpose, alternative, corpus, and the presence of source URLs. The remaining gaps are minor: 'limit' semantics and behavior when no FAQ matches closely.

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 coverage is 50%: 'query' is documented in the schema as a Korean-language question, while 'limit' has only bounds and a default. The description reinforces that the input is a natural-language question matched by closeness, but never mentions the 'limit' parameter or what it controls, so it does not compensate for the uncovered parameter.

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?

States a specific verb and resource: it finds the nearest question among hundreds of Q&A pairs in the published NaeManJip documents. The scope (hundreds of FAQ pairs, public docs) and the contrast with the sibling 'search' let an agent distinguish it without opening either schema.

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?

Explicitly says to use it instead of 'search' when a short, direct answer is wanted, which names the alternative and the selecting condition. It does not spell out the inverse exclusion (e.g., use 'search' for exploratory or non-FAQ material), so it falls just short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.