Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_AUTH_TOKENNoBearer token required when running the server in HTTP mode. The server refuses to start over HTTP without this token set.

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
lookup_rootA

Look up an Arabic root and return all dictionary entries under it.

Accepts a root in any form: "كتب", "ك ت ب", "ك-ت-ب", or with diacritics like "كَتَبَ". Diacritics and letter-variants (ا/أ/إ/آ, ي/ى, ه/ة) are normalized before matching. Use this when the user has already identified the root or when you want to see all sibling words for a lemma.

Returns entries from three sources:

  • arramooz-verb: verb lemma with tense-availability flags in extra

  • arramooz-noun: noun / adjective / participle with wordtype, pattern (wazn), gender/number, and a terse Arabic definition

  • lane-quran: English (and Turkish) semantic gloss from Lane's Lexicon for the ~1,651 roots that occur in the Quran

All returned Arabic words are fully vocalized (tashkeel is preserved from the source, including final case marks) so the caller can tell homographs apart. Input is diacritic-insensitive; output is not.

lookup_wordA

Look up a surface Arabic word (any inflected form or lemma).

Returns matching entries, each labelled with its root — pivot to lookup_root if you want all sibling words. Matching is case- and diacritic-insensitive. Good when the user gives a word but not the root.

search_meaningA

Full-text search over dictionary meanings.

Use when the user asks "what's the Arabic root for X?" or gives a concept in English or Arabic. lang="en" searches English (Lane) glosses; lang="ar" searches Arabic (arramooz) definitions. Results are ranked by relevance and each carries its root, so you can call lookup_root on the best match for full context.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct access path: root lookup, surface word lookup, and meaning search. The descriptions explicitly differentiate when to use each, so there is no ambiguity.

Naming Consistency5/5

All tools follow a clear verb_noun pattern: lookup_root, lookup_word, search_meaning. The pattern is consistent and predictable.

Tool Count5/5

Three tools is well-scoped for a dictionary server. Each tool covers a necessary and non-overlapping function, and the count is within the typical 3-15 range.

Completeness5/5

The tool set covers the full spectrum of dictionary queries: root lookup, word lookup, and semantic search. This provides comprehensive coverage for the domain with no obvious dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues