Skip to main content
Glama
ozumin-dev

irkumo-mcp

by ozumin-dev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IRKUMO_API_KEYYesirkumo API キー (ir_live_... で始まる文字列)。未設定時はエラーとなり終了コード 1 で終了します
IRKUMO_API_BASENoirkumo API のベース URL。ローカル開発時は http://127.0.0.1:8787 などを指定しますhttps://api.irkumo.com
IRKUMO_SITE_URLNoサイトのベース URL。402 残高不足時の購入案内リンクに使用されますhttps://irkumo.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
resolve_companyA

社名や別名から最上位1社を特定してコードと名前と照合情報を返します (消費クレジット: 1。0件時は0)。

search_companiesB

社名や別名から会社候補の一覧を検索します (消費クレジット: 1。0件時は0)。属性列のみ取得可能です。既に持っている列は要求しないようにしてください。

get_companyB

証券コードを指定して1社の詳細情報を取得します (消費クレジット: 指定した列数。1列につき1クレジット)。既に持っている列は要求しないようにしてください。

list_changesB

指定時点以降のデータ変更履歴を取得します (消費クレジット: 返された行数。1行につき1クレジット)。

get_balanceA

現在のクレジット残高とロットの有効期限一覧を取得します (消費クレジット: 0)。

list_fieldsA

利用可能な列の一覧と単価、データの出典情報を取得します (消費クレジット: 0)。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

resolve_company and search_companies both map names/aliases to companies and could be confused, but their descriptions (top-1 with verification vs. a candidate list) differentiate them. get_company (by code) vs. the search tools is clearly distinct, and the utility tools (get_balance, list_fields, list_changes) are unambiguous.

Naming Consistency5/5

All six tools use a consistent snake_case verb_noun pattern (resolve_company, get_balance, list_fields, search_companies, get_company, list_changes). Verbs (resolve/get/list/search) map predictably to their operation type.

Tool Count4/5

Six tools is a tight, well-scoped set for a credit-metered company lookup API, with each tool earning its place. It is slightly thin (no batch/multi-company fetch), but appropriate for the apparent scope.

Completeness4/5

The surface covers the full lookup lifecycle: search=>resolve=>get details, plus field discovery, change history, and balance management, so no obvious dead ends. Only minor gaps like bulk retrieval exist, which an agent can work around by iterating.

Maintenance

ActivityMaintained
ResponsivenessNo issues