FTIR.fun MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FTIRFUN_API_KEY | No | Your FTIR.fun API key. Required for spectrum analysis. The server can start without it for registry introspection. | |
| FTIRFUN_API_BASE_URL | No | Base URL for the FTIR.fun API. | https://ftir.fun |
| FTIRFUN_API_TIMEOUT_SECONDS | No | Timeout in seconds for API calls. | 120 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_ftir_spectrumA | Search the FTIR.fun spectral library for one unknown FTIR spectrum in one call. Use when the user provides an FTIR peak list, a natural-language description containing peaks, or a base64-encoded FTIR instrument file and wants ranked material candidates. Do not use for general chemistry Q&A, non-FTIR spectra, or institutional report review. |
| explain_peaksD | – |
| find_spectraD | – |
| fetch_resultD | – |
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 4 tools
Only one tool has a description, leaving the other three (explain_peaks, fetch_result, find_spectra) ambiguous in purpose. Their names hint at different actions but without descriptions, an agent cannot reliably distinguish them from analyze_ftir_spectrum or each other.
All tools follow a consistent verb_noun pattern with underscores: analyze_ftir_spectrum, explain_peaks, fetch_result, find_spectra. This makes the tool set predictable despite some vague verb choices.
Four tools is appropriate for a focused spectral analysis server. It covers the main interactions (analysis, explanation, result retrieval, library search) without being bloated or too sparse.
The tool set appears to cover core FTIR workflows (analysis, explanation, search, fetch results), but the lack of descriptions for three tools makes it impossible to confirm whether critical operations like peak listing or spectrum comparison are missing. There may be gaps that agents cannot discover.