Skip to main content
Glama

관련 기사

get_related_articles
Read-onlyIdempotent

기사 번호로 같은 주제의 다른 기사를 찾는다(키워드·제목 기준). Related BabyNews articles for an article number.

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": {
      "idxno": "<idxno>"
    },
    "name": "get_related_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
idxnoYes기사 번호
limitNo개수(기본 5, 최대 8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds genuinely useful behavior: relatedness is computed from keywords and title rather than, say, category or author. It does not state ordering or whether results are a fixed-size top-N.

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 scope-defining clause is front-loaded and takes one sentence. The English sentence is essentially a translation of the Korean one, which is mild redundancy rather than added information, but nothing is padded or buried.

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 simple two-parameter read tool with full schema coverage and complete annotations, this is close to sufficient. The one real gap is that there is no output schema, so the description should hint at the return shape (a list of article summaries) and result ordering.

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?

Schema description coverage is 100%: idxno ('기사 번호') and limit (default 5, max 8) are both documented in the schema. The description only restates that the lookup is keyed on the article number, adding nothing about format or how limit affects selection, so the baseline 3 applies.

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: find other articles on the same topic given an article number, qualified by the matching basis (keywords/title). That is clearly distinct from single-article retrieval or plain keyword search. It does not explicitly name a sibling it replaces, so it falls short of a 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?

The intended usage ('by article number, find same-topic articles') is implied rather than spelled out. There is no statement of when to prefer this over search_articles or get_category_articles, and no exclusion or prerequisite 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.