Skip to main content
Glama

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

시공 체크리스트

nmjib_checklist
Read-onlyIdempotent

내만집 시공 체크리스트. phase=pre(공사 전 36항목: 행위허가·주민동의·공사신고·계약·자재·도면), during(공정별: 22공정 시공 확인 항목, process 로 한 공정만), post(공사 후 검수 22항목). "공사 전에 뭘 준비해야 해", "목공 때 확인할 것", "입주 전 검수" 질문에 쓴다.

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": {
      "phase": "<phase>"
    },
    "name": "nmjib_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
phaseYespre=공사 전, during=공정별(공사 중), post=공사 후 검수
processNoduring 일 때 공정 키 또는 한글명(예: mok, 목공, 타일, 도배). 비우면 전체 공정.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is content disclosure — and it delivers scope (36/22/22 items, per-process granularity) that the agent could not infer otherwise, with no output schema to fall back on. It does not describe item format or response structure, keeping it at 4 rather than 5.

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?

Front-loads the core statement, then gives phase details and example questions in a compact three-sentence block with no filler. Minor overlap with the enum descriptions in the schema prevents a 5.

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 supplies the phase content, the process override behavior, and user-facing triggers needed to call it correctly. Only the shape of returned items (fields, ordering) is left implicit, which is a small remaining gap.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it expands what each enum value contains and clarifies that process narrows during to a single process, that Korean names like 목공 are accepted, and that an empty value yields all processes. That goes beyond the enum labels in the schema.

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?

Names the resource precisely (시공 체크리스트) and enumerates what each phase returns — pre with 36 items across named categories, during across 22 processes, post with 22 inspection items. An agent can distinguish this from nmjib_process_guide or nmjib_faq_search purely from the description.

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?

Maps concrete user phrasings to phases ("공사 전에 뭘 준비해야 해" → pre, "목공 때 확인할 것" → during+process, "입주 전 검수" → post), which is strong trigger-based guidance. It does not explicitly say when to prefer a sibling tool instead (e.g. process explanation vs. checklist), so it stops short of a 5.

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.