Skip to main content
Glama

관련 자료 조회

get_related
Read-onlyIdempotent

회계위키의 문단·질의회신·감리지적사례·실무해설 하나를 기준으로 연결된 자료를 종류별로 반환: 그 문단을 인용한 질의회신·감리사례·실무해설, 질의회신이 근거로 든 문단, 관련 토픽, (선택) 내용이 유사한 자료. 기준은 id(search·fetch 결과의 id) 또는 std+para 로 지정. 결과는 이용자 질의에 대한 조회 목적으로만 제공되며 원문 저작권은 제정·발행기관에 있다. 인용 시 응답의 출처 URL 을 표기할 것.

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": "get_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo기준 문서 id (예: 'qna:ifrs/SSI-38683', 'article:lease-overview', 'para:ifrs/1116/main/p22')
stdNo기준서 번호 — id 대신 문단으로 지정할 때 (예: '1116')
paraNo문단 번호 — std 와 함께 (예: '3', 'B34')
domainNostd+para 지정 시 도메인, 기본값 ifrs
include_similarNo임베딩 유사도로 찾은 자료 포함 여부 (기본 false)
limit_per_groupNo종류별 최대 건수, 기본 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "ifrs",
      -  "kgaap",
      -  "audit",
      -  "icfr"
      -]New value: +[
      +  "ifrs",
      +  "kgaap",
      +  "audit",
      +  "icfr",
      +  "law"
      +]
  2. Added

TDQS

A4.3/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 real behavioral context beyond that: results are grouped by material type, similarity results are opt-in via embeddings, and there is a licensing/citation obligation to attribute the source URL from the response. It does not describe result ordering or what an empty group looks like.

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 purpose and the enumerated return types are front-loaded in the opening clause, and the trailing sentences carry the licensing and citation constraints rather than padding. The single very long first sentence packs many clauses together and would read faster split into purpose, input, and return bullets.

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?

With no output schema, the description does the work of describing what comes back by naming the result groups and flagging that similar items are optional. All six parameters are optional and the two anchor modes are explained, so an agent can call it correctly; only the per-group result shape and the behavior when no anchor is given are left unstated.

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 the schema already documents all six parameters, making 3 the floor. The description still adds meaning by explaining that id and std+para are two alternative ways to name the same anchor and by clarifying that the id comes from prior search/fetch output, which the schema only hints at.

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?

States a concrete verb and resource: returns materials linked to a single accounting-wiki item (paragraph, Q&A reply, audit case, practice commentary), enumerated by type. It also spells out both directions of linkage (who cites this paragraph, what this Q&A cites) plus related topics and optional similarity results, which separates it clearly from fetch/search siblings that retrieve by id rather than by relation.

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?

The description tells the agent how to seed the call — by id 'from search/fetch results' or by std+para — which implicitly sequences search/fetch before this tool. It does not state when to skip this tool (e.g. when only the source document is wanted) or name a sibling alternative explicitly, so it stops short of full when/when-not 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.

Resources