Skip to main content
Glama

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

내만집 문서 본문

fetch
Read-onlyIdempotent

search 결과의 id(예: magazine/30pyeong-cost, guide/process-order) 또는 nmjib.com URL 로 문서 전체 본문(마크다운)을 가져온다. 본문 끝에 출처 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes문서 id 또는 https://nmjib.com/... URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral information beyond that: the return is the entire body in markdown and ends with the source URL, which matters because no output schema exists. It does not say what happens for an invalid or missing id.

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?

Two compact sentences with zero filler; the accepted input forms come first and the return-shape note is appended last.

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 tool with rich annotations and documented parameters, the definition covers purpose, accepted inputs, and return shape. The one gap is failure behavior for a bad id or URL, which an agent might want to know.

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 documented, so the baseline is a 3. The description earns the extra point by giving two concrete id format examples and clarifying that a full https://nmjib.com/... URL is accepted in the same field.

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 resource: fetch the full markdown body of a document by id or nmjib.com URL, with two concrete id examples (magazine/30pyeong-cost, guide/process-order). It also implicitly separates itself from the search siblings by noting the id comes from search results, though it never names the search tool outright.

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?

Usage context is clear: this is the follow-up call once you have an id from search results, or an nmjib.com URL. There are no explicit when-not conditions or named alternatives, so it stops short of full routing guidance.

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.