FastMCP Server Template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | HTTP server host for HTTP transport | |
| MCP_HTTP_PATH | No | HTTP endpoint path for HTTP transport | |
| MCP_HTTP_PORT | No | HTTP server port for HTTP transport | |
| MCP_TRANSPORT | No | Transport protocol to use (stdio for local development, http for OpenShift deployment) | |
| MCP_HOT_RELOAD | No | Enable hot-reload for local development | |
| MCP_AUTH_JWT_SECRET | No | JWT secret for symmetric signing (optional authentication) | |
| MCP_REQUIRED_SCOPES | No | Comma-separated required scopes for authentication | |
| MCP_AUTH_JWT_PUBLIC_KEY | No | JWT public key for asymmetric signing (optional authentication) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_fda_deviceB | Unified FDA search tool that accepts any combination of identifiers or descriptive information. Automatically determines optimal search strategy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a clear and distinct purpose focused on FDA device searches.
The single tool name follows a consistent verb_noun pattern (search_fda_device), and with no other tools to compare, there is no inconsistency. The naming is straightforward and descriptive.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. This feels thin and incomplete for any domain beyond a trivial or highly specialized use case.
The tool set is severely incomplete; with only one search tool, there are obvious gaps such as create, update, delete, or other CRUD operations. It lacks coverage for any meaningful lifecycle or domain workflows beyond basic searching.