Skip to main content
Glama
Tai-DT
by Tai-DT

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort to run the server on3000
NODE_ENVNoNode environment (development or production)development
GEMINI_API_KEYYesGemini API key required for AI features
OPENAI_API_KEYNoOptional OpenAI API key for embedding generation

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

Tools

Functions exposed to the LLM to take actions

NameDescription
search_expo_docsB

Search through Expo documentation using semantic search with Gemini AI enhancement

get_expo_examplesA

Get code examples for specific Expo components or APIs using Gemini AI

explain_expo_conceptC

Get detailed explanations of Expo concepts using Gemini AI

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation4/5

Tools are mostly distinct: search discovers relevant docs, get_expo_examples fetches code samples, and explain_expo_concept provides conceptual overviews. There is minor overlap between search and explain for concept queries, but the descriptions make the primary intent clear.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: search_expo_docs, get_expo_examples, explain_expo_concept. This makes the intended action and target clear for each tool.

Tool Count5/5

With only 3 tools, the server is tightly scoped to its purpose of assisting with Expo documentation, examples, and concepts. Each tool serves a distinct needed function without redundancy.

Completeness4/5

The tool set covers the primary ways an agent would interact with Expo documentation: searching, retrieving examples, and getting explanations. A minor gap is the absence of a direct 'get_document' tool for known pages, but search effectively compensates.