Skip to main content
Glama

인용 문구 원문 대조

verify_quote
Read-onlyIdempotent

인용한 문구 하나가 회계위키 원문과 일치하는지 대조. 기준서 문단은 std(+para), 질의회신·감리지적사례·실무해설은 id 로 지정한다. 공백·문장부호 차이는 무시하고 일치(exact)·표현 차이(near)·부분 일치(partial)·불일치(mismatch)로 판정하며, 일치하지 않으면 가장 가까운 원문 문장과 그 문단을 반환. para 를 생략하면 기준서 전체에서 인용문이 있는 문단을 찾는다. 답변 초안의 인용을 한꺼번에 볼 때는 check_citations 가 낫다. 결과는 이용자 질의에 대한 조회 목적으로만 제공되며 원문 저작권은 제정·발행기관에 있다. 인용 시 응답의 출처 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": {
      "quote": "<quote>"
    },
    "name": "verify_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo문서 id — 질의회신·감리지적사례·실무해설·문단 (예: 'qna:ifrs/SSI-38683')
stdNo기준서 번호 (예: '1116', kgaap 은 '13') — id 를 주면 생략
paraNo문단 번호 (예: '22', 'B34') — 생략 시 기준서 전체
quoteYes대조할 인용 문구 (5자 이상)
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. Changed3 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "문서 id — 질의회신·감리지적사례·실무해설·문단 (예: 'qna:ifrs/SSI-38683')",
      +  "type": "string"
      +}
    • changedInput schema / properties / std / description
      Previous value: -"기준서 번호 (예: '1116', kgaap 은 '13')"New value: +"기준서 번호 (예: '1116', kgaap 은 '13') — id 를 주면 생략"
    • changedInput schema / required
      Previous value: -[
      -  "std",
      -  "quote"
      -]New value: +[
      +  "quote"
      +]
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed read, so the bar is lower, yet the description adds real behavior: normalization of whitespace/punctuation, four verdict labels (exact/near/partial/mismatch), and a fallback that returns the nearest source sentence and its paragraph on failure. It also imposes an attribution/legal constraint on downstream use, which annotations do not carry. Only the exact response shape is left implicit, which is a minor gap for a single-verdict tool.

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 core action, then addressing rules, then verdict semantics, then sibling routing, then usage constraints. Every clause is functional, though the licensing/attribution sentences make it noticeably longer than needed for tool selection, and the verdict enumeration is dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 return contract and does: verdict categories, fallback nearest-sentence output, and even a usage obligation on citing the returned source URL. Nothing an agent needs to invoke or interpret the call is missing.

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 baseline is 3, but the description adds a cross-parameter rule the schema only implies: standards paragraphs are addressed via std(+para) while Q&A, audit-case, and practice-commentary items are addressed via id. This clarifying routing between parameters is genuinely useful even though the para-omission behavior is duplicated from the schema.

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 ('인용한 문구 하나가 회계위키 원문과 일치하는지 대조') and immediately distinguishes itself from the batch sibling check_citations. An agent can tell single-quote verification from batch citation checking without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use check_citations when reviewing a whole draft's citations at once, implying this tool is for one quote at a time. It also states the when-omitted behavior for para, so the agent knows calling without para is legal and what happens.

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