Skip to main content
Glama

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

인테리어 비용 참고표

nmjib_cost_reference
Read-onlyIdempotent

평형(20·24·30·33·40평)·공간(욕실·주방·현관·거실·베란다 등)·공정(도배·타일·마루·필름·샤시·조명 등) 30개 주제의 비용 범위. 내만집 매거진이 실제 후기를 집계해 적은 문장과 기준일·출처 글 URL 을 돌려준다. 단가·견적 금액이 아닌 후기 집계 범위다. topic 을 주면 그 주제만.

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

Input Schema

NameRequiredDescriptionDefault
topicNo주제(예: "30평", "욕실", "도배", "샷시"). 비우면 전체 표.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description still adds real behavioral value beyond that: it discloses the provenance of the data (aggregated from actual 후기 by 내만집 매거진) and the returned fields (문장, 기준일, 출처 글 URL), letting the agent judge freshness and citability. It does not cover volume/size of the full table or any truncation behavior.

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-loaded with the taxonomy that an agent needs to pick a topic, followed by return contents, then the caveat, then the parameter behavior. Every sentence carries information; the only minor cost is that the taxonomy sentence is dense with enumeration.

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 one-parameter, read-only reference lookup with no output schema, the definition supplies what the agent needs: valid topic axes, what comes back (text, reference date, source URL), and the caveat that values are aggregated review ranges rather than prices. Only the shape/size of the full-table response when `topic` is omitted remains unspecified.

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?

The single `topic` parameter is already 100% described in the schema with examples, so the baseline is 3. The description goes further by laying out the valid topic vocabulary (평형/공간/공정 with concrete values like 20·24·30·33·40평, 욕실·주방·현관, 도배·타일·마루), which meaningfully helps the agent construct a valid value, and it clarifies the default-to-full-table behavior when omitted.

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 names the resource precisely (cost ranges for 30 topics) and enumerates the three axes of the taxonomy: 평형, 공간, 공정, with example values. It also draws a boundary that matters for selection — '단가·견적 금액이 아닌 후기 집계 범위다' — which separates it from a quoting/pricing tool. It stops short of naming a specific sibling as the alternative, so it lands at 4 rather than 5.

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 by the subject matter (look up a cost ballpark) and the exclusion of exact quotes nudges the agent away from using it for quotations. However, there is no explicit statement of when to prefer this over nmjib_material_catalog or nmjib_consult_request, and no prerequisites are given. The 'topic 을 주면 그 주제만' line is about invocation, not tool selection.

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.