Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_capabilitiesA

Report which NLP engines are installed and which capabilities each language supports. Always call this first if unsure what is available.

tokenizeA

Segment text into tokens with exact character offsets.

Chinese: jieba by default; English: spaCy when installed, then stanza, then a regex fallback. engine may force one: "jieba" | "spacy" | "stanza" - an unavailable forced engine raises an actionable install hint instead of being silently ignored. lang: "auto" | "zh" | "en" | any stanza language code (fr, de, ja, ...).

pos_tagA

Part-of-speech tagging (+ lemma with stanza). Chinese: jieba.posseg; English: spaCy then stanza; other languages: stanza. engine may force one: "jieba" | "spacy" | "stanza" - use engine="stanza" to get UPOS + lemma even when spaCy is installed. An unavailable forced engine raises an actionable install hint instead of being silently ignored.

nerA

Named entity recognition with exact spans.

Chinese: stanza statistical NER when installed (recommended), otherwise the jieba POS-tag heuristic (nr/ns/nt -> PER/LOC/ORG). English: spaCy, then stanza. Other languages: stanza. engine may force one: "jieba" | "spacy" | "stanza" - an unavailable forced engine raises an actionable install hint instead of being silently ignored.

keyword_extractB

Keyword extraction with weights. Chinese: jieba TF-IDF or TextRank. English: word-frequency fallback (honest, cheap, deterministic).

sent_splitA

Sentence segmentation with offsets - the foundation for RAG chunking. Chinese: jieba + rule regex; English: spaCy sents by default, or the zero-dependency regex fallback with engine="regex" - use the fast path for bulk preprocessing where neural segmentation is not worth the CPU time.

openie_triplesA

Open Information Extraction: (subject, predicate, object) triples.

Engine priority for English (engine may force one):

  1. corenlp - the canonical Stanford CoreNLP OpenIE via a local CoreNLP server (env CORENLP_URL, default localhost:9000) when it is up;

  2. spacy - dependency-parse rules (confidence 0.6).

Chinese: naive (noun, verb, noun) pattern mining over jieba POS (confidence 0.35 - draft quality by design). CoreNLP's OpenIE is English-focused. Every triple carries the source character span and is a candidate for downstream KG normalization - not a fact.

constituency_parseB

Phrase-structure (constituency) parses via stanza - exclusive to the Stanford stack among the wrapped engines. Returns bracketed trees plus the set of node labels per sentence. Requires the language's stanza models with the 'constituency' processor.

dependency_parseA

Neural/statistical dependency parse: head, relation label, POS and morphological features per word (universal-dependencies for stanza).

English: spaCy (en_core_web) by default, stanza also available. Chinese: stanza only - spaCy zh labels are coarse; jieba cannot parse. This is the entry point for syntax-aware extraction: definitional clauses, subject/object probing, syntactic patterns - far above keyword statistics.

noun_phrasesB

Extract base noun phrases (chunking) with spans and syntactic roots.

English: spaCy's statistical chunker. Chinese: jieba rule-merge of consecutive noun tokens (a heuristic, honestly labeled), or the stanza engine via dependency_parse for higher quality. Noun phrases are the natural topic units - cleaner than raw keyword statistics.

sentimentA

Sentiment classification with pretrained models.

English: NLTK VADER (valence lexicon, compound score). Chinese: stanza neural classifier (REN model) with per-sentence labels - a trained model, not a lexicon lookup. Use auto to get the best installed engine.

seme_lookupB

HowNet sememe (义原) lookup for a Chinese word via OpenHowNet. Fine-grained interpretable lexical semantics - useful for entity typing and sememe-based similarity.

wordnet_lookupB

WordNet synsets, definitions, synonyms and hypernyms for an English word via NLTK.

wordnet_similarityB

Best WordNet path similarity between two English words via NLTK.

annotate_fullA

Run every available capability in one call and merge the results - one round trip instead of seven.

Includes tokenize/pos/ner/keywords/sent_split/openie; adds seme_lookup/wordnet lookups when with_semantics is true and the corresponding libraries are installed. Failed sub-capabilities are reported per-key under errors with actionable install hints instead of failing the whole call.

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 15 tools

Disambiguation4/5

Each tool targets a clearly distinct NLP capability, and the descriptions actively distinguish the near-neighbors (e.g. dependency_parse vs constituency_parse, noun_phrases vs keyword_extract vs openie_triples). The only mild overlap is between the individual analyzers and annotate_full, which is explicitly framed as an aggregator.

Naming Consistency4/5

All names are snake_case, which is consistent, and most combine a domain noun with an operation (pos_tag, sent_split, seme_lookup, wordnet_similarity). A few deviate from a strict verb_noun pattern (plain 'tokenize', 'ner', 'sentiment' as bare capability names), but the set is still highly predictable.

Tool Count5/5

Fifteen tools sit squarely in the well-scoped range for an NLP toolkit, and each maps to a distinct capability (plus one legitimate aggregate). Nothing feels redundant or padded.

Completeness4/5

The surface covers a full classic NLP pipeline: tokenization, POS/lemma, NER, keywords, sentence splitting, constituency/dependency parsing, noun phrases, OpenIE, sentiment, and lexical semantics, plus a batch aggregator. Minor gaps remain (no standalone language detection, coreference, or summarization/classification beyond sentiment), but core workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues