Skip to main content
Glama
yuma-shin

rokadoc MCP Server

by yuma-shin

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROKADOC_API_KEYYesrokadoc APIの認証キー
ROKADOC_BASE_URLNorokadoc APIのベースURL。オンプレミス環境の場合は変更可能。https://api.rokadoc.ntt.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
convert_documentB

ドキュメントファイルをrokadocに送信して構造化テキストに変換する

list_conversionsC

変換ジョブの一覧を取得する

get_conversion_resultC

指定された変換ジョブの結果を取得する

search_documentsB

rokadocに登録されたドキュメントに対してRAG検索を実行する

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct action on a distinct resource: submitting a conversion, listing jobs, fetching a job result, and RAG-searching documents. There is no meaningful overlap between the submission and retrieval tools, and search_documents is clearly separate.

Naming Consistency5/5

All four tools follow a consistent snake_case verb_noun pattern (list_conversions, get_conversion_result, search_documents, convert_document). No deviations in style or convention.

Tool Count4/5

Four tools is a reasonable, focused surface for a document conversion + RAG service, though it leans slightly thin. Each tool earns its place without redundancy.

Completeness3/5

The core workflow (submit conversion, list jobs, fetch result, search) is covered, but there is no way to delete or cancel a conversion/document or fetch document metadata. These gaps limit lifecycle management.

Maintenance

ActivityActive
ResponsivenessUnresponsive