Skip to main content
Glama
peter-j-thompson

Semantic API

by peter-j-thompson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SEMANTIC_API_KEYYesYour Semantic API key
SEMANTIC_API_URLNoAPI base URL overridehttps://semanticapi.dev

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
semantic_queryA

Search for an API capability using natural language.

Returns endpoint details, parameters, auth info, and code snippets.

Args:
    query: Natural language description of what you want to do (e.g. "send an email with Gmail")
    auto_discover: Whether to automatically discover new APIs if no cached result exists
semantic_discoverC

Deep discovery of a specific provider/API by name and intent.

Args:
    provider_name: Name of the API provider (e.g. "stripe", "twilio", "github")
    user_intent: Optional description of what you want to do with this API
semantic_discover_urlB

Analyze any API from its documentation URL. Generates a full provider config.

Args:
    url: URL of the API documentation to analyze
    user_intent: Optional description of what you want to do with this API

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

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: semantic_discover targets APIs by provider name, semantic_discover_url analyzes documentation URLs, and semantic_query searches via natural language. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent 'semantic_' prefix pattern with descriptive suffixes (discover, discover_url, query). This uniformity enhances readability and predictability, adhering to a clear naming convention throughout.

Tool Count4/5

With 3 tools, the count is slightly low but reasonable for the server's purpose of API discovery and querying. It covers key operations (discovery by name, URL, and natural language), though additional tools for managing or testing discovered APIs could enhance completeness.

Completeness3/5

The tools provide good coverage for discovering and querying APIs, but there are notable gaps in lifecycle management. For example, there are no tools for saving, updating, or deleting discovered API configurations, which could limit agent workflows in a full API integration scenario.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources