Skip to main content
Glama

질의회신 조회

get_qna
Read-onlyIdempotent

회계위키의 질의회신·감리지적사례 전문 조회 (slug 는 search 결과 또는 페이지 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": {
      "slug": "<slug>"
    },
    "name": "get_qna"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes질의회신 슬러그 (예: 'SSI-38683')
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds value beyond that by disclosing licensing constraints: results are for user-query reference only, copyright belongs to the issuing body, and the source URL must be cited. Return format is not described, but with no output schema that is a minor gap.

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?

Front-loaded with the operation and resource in the first clause, then the slug-source parenthetical, then the licensing note. Three sentences, each carrying distinct information. The copyright sentence is slightly tangential to tool selection but is defensible as licensing context the agent must convey.

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 two-parameter read-only lookup, the definition covers purpose, how to obtain the required identifier, and usage/licensing constraints. The main omission is any hint about the shape of the returned full text, which matters because there is no output schema. Everything else an agent needs to invoke it correctly is present.

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 both parameters are already documented (slug with the 'SSI-38683' example, domain enum with default ifrs). The description nevertheless adds genuine meaning by explaining where the slug value originates — search results or the last path segment of a page URL — which the schema does not say. The domain parameter is left entirely to 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?

'질의회신·감리지적사례 전문 조회' names a specific verb (retrieve full text) and a specific resource (Q&A replies / audit inspection cases), which is distinct from a generic search. It also tells the agent where the slug comes from, implicitly contrasting this with the retrieval-by-query siblings. It stops short of explicitly naming when to prefer it over get_standard or get_topic.

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 parenthetical that the slug comes from 'search 결과 또는 페이지 URL 마지막 경로' implies the intended workflow: run a search first, then fetch. The remaining guidance is about downstream citation obligations rather than when-not-to-use or alternative tools. No explicit exclusions or prerequisites (auth, rate limits) are stated.

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