Skip to main content
Glama

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

인테리어 공정 순서·일수표

nmjib_process_guide
Read-onlyIdempotent

반셀프 인테리어 공정 순서 22단계(보양→철거→설비→…→마감)와 평형별 표준 풀리모델링 영업일(15~65평, 내만집 일정 엔진 계산값 — 병행 공정·양생 대기일·예비 포함). 평수를 주면 그 평수의 막대별 영업일·일차와 공기를 돌려준다. "공정 순서", "며칠 걸리나", "도배 마루 뭐가 먼저" 질문에 쓴다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nmjib_process_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
pyeongNo공급/전용 평수(기본 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world lookup, so the lower bar applies. The description still adds meaningful provenance beyond them: the day counts are engine-computed and already fold in parallel trades, curing wait days, and buffers, which tells the agent how to interpret and trust the numbers.

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?

The definition is dense but front-loaded: it leads with what the table contains, then what the call returns, then the trigger questions. A few enumerations (step chain, parenthetical qualifiers) are slightly heavy, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a single optional parameter, the description carries the remaining burden and does so: it explains both the sequence content and the shape of the returned schedule. An agent has enough to decide and call correctly.

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% and the single parameter is fully documented, so the baseline is 3. The description earns an extra point by disclosing that the table covers 15–65 pyeong, a narrower band than the schema's 10–80 bounds, which warns the agent that out-of-band inputs may not return meaningful data.

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?

The description names a specific resource (22-step interior construction sequence plus per-pyeong standard business-day table) and states precisely what a call returns (per-milestone business days, day offsets, and total duration). It is clearly distinct from the cost, material, and FAQ siblings without needing to name them.

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?

It gives explicit trigger questions — process order, how many days it takes, and precedence questions like wallpaper vs. flooring — which is concrete when-to-use guidance. It stops short of stating when not to use it or which sibling to prefer for adjacent needs (e.g., cost estimates).

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.