Skip to main content
Glama

기준서 문단 조회

get_paragraphs
Read-onlyIdempotent

회계위키에서 기준서의 특정 문단들을 번호로 조회 (예: std='1116', paras=['22','B34']). 적용지침(B)·결론도출근거(BC) 문단도 토큰으로 자동 해석. 문단마다 본문이 가리키는 문단과 같은 기준서에서 그 문단을 가리키는 문단 번호를 덧붙인다 - 조건·예외를 정하는 문단이므로 함께 읽을 것. 결과는 이용자 질의에 대한 조회 목적으로만 제공되며 원문 저작권은 제정·발행기관에 있다. 인용 시 응답의 출처 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": {
      "std": "<std>",
      "paras": "<paras>"
    },
    "name": "get_paragraphs"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdYes기준서 번호 (예: '1116', kgaap 은 '13')
parasYes문단 번호 목록 (예: ['22','한54.2','B34','BC78'])
domainNo기본값 ifrs

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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds real behavior: B/BC tokens are auto-resolved, and each result is augmented with the paragraph numbers it references and that reference it. The citation and copyright notice further clarifies usage constraints. It stops short of describing result shape or limits (e.g., max 20 paragraphs handled per call).

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?

Purpose and example are front-loaded and the sentences are dense but purposeful. The trailing licensing/citation boilerplate is the weakest part, taking space without helping an agent invoke the tool.

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?

No output schema exists, so the description carries the burden of describing returns; it does explain the cross-reference augmentation and the source URL, which is enough to interpret results. It is slightly incomplete on the overall record structure and on the 'domain' parameter's effect across ifrs/kgaap/audit/icfr/law.

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 coverage is 100%, so the baseline is 3. The description does add one useful nuance beyond the schema by explaining that B-prefixed and BC-prefixed tokens are interpreted as application guidance and basis-for-conclusions paragraphs respectively, but it says nothing about the 'domain' parameter or the paragraph-number format variants (e.g., '한54.2').

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 specific verb and resource ('기준서의 특정 문단들을 번호로 조회') with a concrete call example (std='1116', paras=['22','B34']), making the paragraph-level granularity unmistakable against the whole-standard sibling get_standard.

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 'look up by number' framing implies usage, and the instruction to read cross-referenced paragraphs together because they set conditions/exceptions is genuine handling advice. However, it never states when to prefer this over get_standard or a text search, nor any precondition such as needing a known paragraph number.

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