Skip to main content
Glama

기준서 목록

list_standards
Read-onlyIdempotent

회계위키에 수록된 도메인의 기준서 전체 목록 (번호·제목·문단수·URL). 결과는 이용자 질의에 대한 조회 목적으로만 제공되며 원문 저작권은 제정·발행기관에 있다. 인용 시 응답의 출처 URL 을 표기할 것.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_standards"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: the exact fields returned, that the listing covers the entire domain (no filtering or pagination implied), and a copyright/citation obligation on downstream use. Missing only notes on size or rate limits.

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?

Three short sentences, front-loaded with what the tool returns, followed by the legal/citation constraints. The copyright sentence is boilerplate but carries a real obligation the agent must honor when citing, so it earns its place.

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 single-optional-parameter listing tool with no output schema, the description supplies the return shape, the domain scope, and citation rules. Nothing essential for correct invocation is missing; only cross-references to sibling tools would improve it.

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 description coverage is 100% and the single parameter carries an enum of five values with a stated default of ifrs, so the schema does all the work. The description only alludes to domain scoping without enumerating the domains or explaining what each covers, which is the baseline-3 case.

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 states a specific verb and resource ('회계위키에 수록된 도메인의 기준서 전체 목록') and enumerates the returned fields (번호·제목·문단수·URL), so an agent knows this is a complete domain listing rather than a lookup of one item. It does not explicitly contrast itself with the sibling get_standard, which is the only thing keeping it from a 5.

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 context is implied: it is a listing/browsing tool scoped to a domain, and the description adds a licensing constraint ('조회 목적으로만 제공') plus a citation obligation. However, it never says when to prefer this over get_standard, search, or find_evidence, and gives no exclusions, so selection guidance is left to inference.

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