Japanese Text Analyzer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| count_charsA | ファイルの文字数を計測します。絶対パスを指定してください(Windows形式 C:\Users...、またはWSL/Linux形式 /c/Users/... のどちらも可)。スペースや改行を除いた実質的な文字数をカウントします。 |
| count_wordsA | ファイルの単語数を計測します。絶対パスを指定してください(Windows形式 C:\Users...、またはWSL/Linux形式 /c/Users/... のどちらも可)。英語ではスペースで区切られた単語をカウントし、日本語では形態素解析を使用します。 |
| count_clipboard_charsB | テキストの文字数を計測します。スペースや改行を除いた実質的な文字数をカウントします。 |
| count_clipboard_wordsA | テキストの単語数を計測します。英語ではスペースで区切られた単語をカウントし、日本語では形態素解析を使用します。 |
| analyze_textC | テキストの詳細な形態素解析と言語的特徴の分析を行います。文の複雑さ、品詞の割合、語彙の多様性などを解析します。 |
| analyze_fileC | ファイルの詳細な形態素解析と言語的特徴の分析を行います。文の複雑さ、品詞の割合、語彙の多様性などを解析します。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
There is significant ambiguity between tools: analyze_file and analyze_text appear to do the same analysis but on different inputs (file vs. text), while count_chars and count_clipboard_chars both count characters with similar descriptions, and count_words and count_clipboard_words both count words with similar logic. This overlap can easily lead to misselection by an agent.
The naming follows a consistent verb_noun pattern throughout (e.g., analyze_file, count_chars), with all tools using snake_case. However, the use of 'clipboard' in some names deviates slightly from the file/text distinction in others, but overall the pattern is predictable and readable.
With 6 tools, the count is reasonable for a text analysis server, as it covers multiple aspects like analysis and counting. It's slightly on the higher side due to duplication, but not excessive, and each tool serves a purpose within the domain.
The server covers core text analysis and counting functions, but there are notable gaps: it lacks tools for operations like summarization, sentiment analysis, or editing, which are common in text processing. The surface is functional but not comprehensive for advanced text analysis workflows.