Skip to main content
Glama
shnkreddy98

Universal Adapter

by shnkreddy98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_HOSTNoHost for MCP server (default: 0.0.0.0).
MCP_PORTNoPort for MCP server (default: 8002).
MONGODB_URINoMongoDB connection string. Defaults to mongodb://localhost:27017/agent_db if not set.
VOYAGE_API_KEYNoOptional API key from Voyage AI for semantic tool search embeddings. App works without it.
FIRECRAWL_API_KEYYesAPI key from Firecrawl.dev (required for web search/scrape).
OPENROUTER_API_KEYYesAPI key from OpenRouter.ai (required for chat).

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
chatA

Chat with the Universal Adapter agent.

The agent has access to all marketplace tools including:

  • File operations (read, write, list)

  • Web scraping (firecrawl search, scrape, crawl)

  • Tool generation (generate new tools from API docs)

  • Tool search (semantic search of marketplace)

  • All dynamically generated tools (crypto prices, APIs, etc.)

Args: message: Your question or command conversation_id: Optional conversation ID for multi-turn chat model: LLM model to use (default: claude-haiku-4.5) max_iterations: Maximum agent iterations (default: 25)

Returns: dict: Response with agent output, conversation_id, usage stats

list_marketplace_toolsA

List available tools in the marketplace.

Args: limit: Maximum number of tools to return

Returns: dict: List of tools with names and descriptions

healthA

Check if the MCP server is healthy

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

The three tools serve completely distinct purposes: interactive chat, listing marketplace tools, and health checking. There is no overlap or ambiguity between them.

Naming Consistency3/5

Naming is a mix of a bare verb (chat), a noun (health), and a verb_noun phrase (list_marketplace_tools). This is not a consistent pattern, though all names are lowercase with underscores and are readable.

Tool Count5/5

Three tools is an appropriate scope for an adapter server whose primary interface is a chat agent. Each tool has a clear role and none feels superfluous.

Completeness4/5

The chat tool exposes broad marketplace capabilities, and list_marketplace_tools provides discovery. A minor gap is the lack of a direct get-tool-details endpoint, but this is not critical since chat can retrieve such information.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources