Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EXA_API_KEYYesYour Exa API key

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": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchC

Perform a web search using Exa.

find_similarC

Find pages similar to a given URL using Exa.

get_contentsB

Retrieve contents for a list of URLs using Exa.

answerB

Generate an answer to a query using Exa's search and LLM capabilities.

stream_answerC

Generate a streaming answer response using Exa.

research_createB

Create a new research request using Exa.

research_getB

Get a research request by ID using Exa.

research_poll_until_finishedA

Poll until research is finished using Exa.

research_listC

List research requests using Exa.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 9 tools

Disambiguation3/5

Most tools have clear boundaries (search, get_contents, find_similar, research_*), but answer and stream_answer are nearly identical except for streaming behavior, which could cause misselection. find_similar and search are related but distinct enough with descriptions.

Naming Consistency3/5

The research_* tools follow a consistent prefix pattern, but the rest mix bare verbs (search, answer), verb_noun (find_similar, get_contents, stream_answer), and a long descriptive phrase (research_poll_until_finished), creating an inconsistent feel.

Tool Count4/5

9 tools is a reasonable size for a search and research server, covering immediate searches, content retrieval, and async research workflows. Slightly more than strictly necessary due to answer/stream_answer duplication, but not excessive.

Completeness4/5

The core search, similar, content, answer, and research lifecycle (create, get, poll, list) are covered. A notable gap is the lack of a cancel/delete research operation, but most main workflows are complete.

Maintenance

ActivityInactive
ResponsivenessNo issues