Skip to main content
Glama

회계위키 검색

search
Read-onlyIdempotent

회계위키 전체(기준서 문단·질의회신·감리지적사례·실무해설) 검색. 키워드와 뜻(의미)을 함께 보므로 '리스료를 깎아주면 어떻게 처리하나'처럼 문장으로 물어도 된다. 기준서 용어·문서번호는 정확히 일치하는 결과가 위로 온다. 실무 표현으로 찾은 결과가 약하면 기준서 용어로 바꿔 한 번 더 검색할 것(예: '계약 따낸 대가로 준 수수료' → '계약체결 증분원가', '앱마켓 수수료 빼고 매출' → '본인 대 대리인'). 질문에 대한 근거를 한 번에 모으려면 find_evidence 가 낫다. 결과의 id 를 fetch 에 넘기면 전문을 얻는다. 결과는 이용자 질의에 대한 조회 목적으로만 제공되며 원문 저작권은 제정·발행기관에 있다. 인용 시 응답의 출처 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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdNo기준서 번호로 한정 (예: '1116')
kindNostandard: 기준서 문단만, qna: 질의회신·감리사례만, article: 실무해설만
limitNo기본 10
queryYes검색어 (예: '리스 변경 회계처리')
domainNo도메인 필터 — 생략 시 전체 도메인 검색

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. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"standard: 기준서 문단만, qna: 질의회신·사례만"New value: +"standard: 기준서 문단만, qna: 질의회신·감리사례만, article: 실무해설만"
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "standard",
      -  "qna"
      -]New value: +[
      +  "standard",
      +  "qna",
      +  "article"
      +]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower; the description still adds real behavioral detail the annotations cannot express — hybrid keyword+semantic matching, ranking preference for exact standard terminology and document numbers, and a retrieval-quality heuristic for when to re-query. It also discloses a licensing/citation constraint, instructing the agent to attribute the source URL, which is an obligation not present in any structured field.

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 purpose, then query strategy, then the alternative tool, then result handling and citation terms — a sensible funnel. The copyright/citation sentence is partly boilerplate and the parenthetical examples make it dense, but every clause is actionable for an agent.

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?

With no output schema, the description correctly fills the gap by explaining that results carry ids usable with fetch and source URLs usable for citation. Combined with the query-reformulation guidance and the find_evidence pointer, an agent has everything needed to call correctly and act on results.

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% with enums documented, so the schema carries most of the load; the description still adds meaning for the required `query` param (sentences work, not just keywords) and implies how `std`/document numbers affect ranking (exact matches float up). It does not explain limit or domain behavior beyond the schema, so it is not a full 5.

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?

The opening sentence gives a specific verb (검색) plus an explicit scope enumeration (기준서 문단·질의회신·감리지적사례·실무해설), so an agent knows exactly what corpus is covered. It also distinguishes itself implicitly from narrow siblings like get_paragraphs or get_qna by covering the whole wiki.

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 states that full natural-language questions are acceptable, that exact standard terms/document numbers rank higher, and gives a concrete fallback strategy with two worked rewrites ('계약 따낸 대가로 준 수수료' → '계약체결 증분원가'). It also names the alternative route: use find_evidence to gather support for a question in one pass, and fetch to expand an id into full text.

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