Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EXA_API_KEYNoAPI key for the Exa search engine. Missing engine keys cause that engine to be skipped rather than failing the search.
BRAVE_API_KEYNoAPI key for the Brave search engine. Missing engine keys cause that engine to be skipped rather than failing the whole search.

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
searchB

Parallel multi-engine web search with RRF fusion and Jina reranking. Returns JSON with ranked results, engine provenance and engine health.

fetchC

Fetch page text. Tries the DeepSeek Fetch API first (no container), then a static -> dynamic -> stealth container ladder.

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

Disambiguation5/5

Search and fetch have clearly separate roles: search discovers ranked results across engines, while fetch retrieves the full text of a specific URL. An agent can easily decide which to use with no overlap.

Naming Consistency5/5

Both tool names are single, concrete verbs (search, fetch) following a consistent action-oriented convention. There is no mixing of casing or verb styles.

Tool Count3/5

Two tools is thin for a search aggregation server, though both are essential to the core workflow. The surface feels minimal and could reasonably include health or configuration operations.

Completeness4/5

The search-plus-fetch pair covers the main retrieval pipeline well. Minor gaps exist, such as no dedicated engine-health or batch-fetch operation despite health data being referenced in search output.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues