Deterministic Japanese Parser MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_japaneseC | Deterministically read Japanese text and return lexical meaning, predicate-argument structure, negation/condition/modality scope, quotation attribution, discourse relations, a MeaningGraph, and downstream TaskGraph and external-action safety decisions. |
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 1 tool
Only one tool is exposed, so there is no overlapping purpose or selection ambiguity. Its purpose is clearly stated as deterministic Japanese text analysis.
The single tool name analyze_japanese follows a clear verb_noun snake_case convention. With only one tool, there are no deviations or competing conventions to assess.
One tool is borderline thin for a parser that claims to return lexical, syntactic, semantic, discourse, graph, and safety outputs. A single entry point can be reasonable, but the breadth suggests it could benefit from focused sub-tools.
The tool covers a broad parsing pipeline from lexical meaning through discourse relations and downstream task graphs. Minor gaps may exist for configuration, batch input, or custom dictionary handling, but the core parsing surface appears well covered.