Skip to main content
Glama

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

내만집 문서 검색

search
Read-onlyIdempotent

내만집(nmjib.com)의 반셀프 인테리어 공개 문서를 검색한다 — 매거진 165편(비용·공정·후기), 방식별 안내(반셀프·셀프·부분·견적), 가이드 36장(공정 순서·일수표, 공사 전/후·공정별 체크리스트, 비용 참고표, 공정별 인원·일수표, 그리고 질문형 가이드: 반셀프·턴키·셀프 비교, 작업자 구하는 법, 행위허가·주민동의·공사신고, 견적서 비교, 철거 범위, 실패 패턴 집계, 20·30평대 허브, 공정표 양식, 견적 받는 법, 욕실 리모델링, 도배·마루 순서, 매수 전·잔금 당일 점검, 구축 천장, 실측 순서, 원거리 집주인, 시스템에어컨 설치, 행위허가 직접 vs 대행, 누수 연락, 확장 타일, 샷시 고르기, 입주청소, 관리사무소 질문, 대출 일정, 생활 흠집, 동의서 받기, 철거 뒤 발견, 석고보드·단열재 위 마감, 입주 뒤 등 더 달기). 한국어 자연어 질의. 결과의 id 를 fetch 에 넘기면 본문을 받는다.

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

Input Schema

NameRequiredDescriptionDefault
kindNo문서 종류로 제한(선택)
limitNo결과 수(기본 8)
queryYes검색어(한국어). 예: "30평 반셀프 인테리어 비용", "도배 마루 순서"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the corpus is public documents only, retrieval is two-step (search, then fetch by returned id), and queries should be Korean natural language.

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

Conciseness2/5

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

The purpose is front-loaded, which is good, but roughly half the text is a runaway enumeration of ~30 individual guide titles nested inside a parenthetical. That list adds little routing value over a single sentence such as 'guides cover cost, process order, checklists, and FAQ-style comparisons', and it buries the far more important two-step fetch instruction at the end.

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?

For a 3-parameter search tool with no output schema, the definition covers what is searched, how to query it, and the crucial handoff of the returned id to fetch. It stops short of describing the rest of the result shape (titles, snippets, total counts) or ranking/pagination behavior, leaving some guesswork about what actually comes back.

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?

With schema description coverage at 100% (query examples, kind enum, limit bounds/default), the schema does the heavy lifting, so the baseline is 3. The description only reinforces the query format with '한국어 자연어 질의' and never mentions how kind or limit should be chosen.

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 (내만집 공개 문서), scoped to a known corpus of magazines, method guides, and 36 guides. It is distinguishable from a generic search, but it does not differentiate itself from siblings such as nmjib_faq_search, nmjib_checklist, nmjib_cost_reference, or nmjib_process_guide, even though it claims to cover checklist and cost-table content that those tools appear to target.

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?

It gives a useful if brief usage signal: '한국어 자연어 질의' plus a follow-up workflow '결과의 id 를 fetch 에 넘기면 본문을 받는다'. However, there is no guidance on when to pick this tool over the 12 sibling tools that seem dedicated to specific content, so the agent must guess.

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.