Skip to main content
Glama
memorise8

dart-search-mcp

by memorise8
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_xbrl_taxonomy

Retrieve XBRL taxonomy financial statement templates by division (BS, IS, CF, SCE). Returns standard account items including ID, name, and display order.

Instructions

XBRL 택사노미 재무제표 양식(표준계정과목체계)을 조회합니다.

Parameters:
    sj_div: 재무제표구분
        BS1=재무상태표(일반), BS2=재무상태표(특수), BS3=재무상태표(은행),
        BS4=재무상태표(보험), IS1=손익계산서(일반), IS2=손익계산서(특수),
        IS3=손익계산서(은행), IS4=손익계산서(보험),
        DCIS=포괄손익계산서, CF1~CF4=현금흐름표, SCE=자본변동표

Returns:
    표준계정과목 목록 (계정ID, 계정명, 표시순서 등)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sj_divNoBS1

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It only states it returns a list of accounts, but no info on idempotency, permissions, rate limits, or side effects. For a read-only query, this is minimal.

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?

The description is concise, starting with purpose then parameter details. The parameter list is lengthy but necessary. No fluff.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with one parameter and an output schema exists, reducing burden. However, it lacks guidance on how to use the taxonomy (e.g., with financial statement tools). Adequate but not complete.

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?

Despite 0% schema coverage, the description adds detailed enumeration of possible sj_div values with Korean labels, which is essential for correct parameter usage. This compensates well for the schema gap.

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 clearly states the tool queries XBRL taxonomy financial statement forms (standard account system). It distinguishes from siblings like get_financial_statements by focusing on the taxonomy structure, but does not explicitly differentiate.

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

Usage Guidelines2/5

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

No indication of when to use this tool versus alternatives. No criteria for choosing sj_div values or when not to use. The description only lists parameters without context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/memorise8/dart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server