Skip to main content
Glama

기준서 목차·섹션 조회

get_standard
Read-onlyIdempotent

회계위키에서 기준서의 목차(섹션·문단 범위)와 메타데이터 조회. section 지정 시 해당 섹션 본문 전체를 반환. 전문 마크다운은 응답의 .md 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": {
      "std": "<std>"
    },
    "name": "get_standard"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdYes기준서 번호 (예: '1116')
domainNo기본값 ifrs
sectionNo섹션 제목 (목차에 나온 제목, 부분 일치 허용)

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: section lookups return the entire section body, the full markdown is also exposed via a .md URL in the response, and the results carry licensing/citation obligations that require attributing the source URL.

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?

Four short sentences, front-loaded with what the tool returns, followed by parameter behavior, delivery format, and the licensing/citation constraint. Every sentence contributes distinct information with no redundant restatement of the schema.

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 read-only, three-parameter tool with fully documented schema and no output schema, the description covers purpose, drill-down behavior, and where the full text lives (.md URL), which is what an agent needs to call it correctly. It could be marginally stronger by naming the alternative tool for paragraph-level retrieval.

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 description coverage is 100%, so the baseline is 3; the description earns above baseline by explaining the consequence of the section parameter (returns the whole section body rather than a pointer) and by disclosing that the full document markdown is accessible through a .md URL, which is not visible in the schema.

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 uses a specific verb+resource pair: it retrieves a standard's table of contents (section and paragraph ranges) and metadata, and it explains that supplying a section returns that section's full body. This is clearly differentiated in behavior, but no sibling tool (e.g. get_paragraphs, list_standards) is named, so the agent must infer the boundary itself.

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 rather than stated: listing a TOC and fetching a section body suggests 'call this to navigate a standard,' and the section parameter is framed as the drill-down path. However, there is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternative tools for paragraph-level or search-based retrieval.

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