RateSpot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-mortgage-ratesD | – |
| get-streaming-resultsD | – |
| save-streaming-resultsD | – |
| list-saved-resultsD | – |
| analyze-fileD | – |
| read-fileD | – |
| list-directoryD | – |
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 7 tools
The tools are split across unrelated domains—mortgage rates, streaming results, and file operations—so broad purposes are clear. However, 'get-streaming-results' and 'list-saved-results' could easily be confused, and 'analyze-file' vs 'read-file' overlap in intent.
All tool names use a consistent lowercase kebab-case format with a verb-object pattern (get-, save-, list-, analyze-, read-). Minor inconsistency exists in mixing 'streaming-results' and 'saved-results', but the overall pattern is predictable.
Seven tools is a reasonable count and not overwhelming. The count feels slightly scattered because it appears to cover at least three unrelated domains, but no individual tool seems redundant enough to cut.
The tool set lacks a clear central domain, making it hard to assess complete coverage. Mortgage rates have only a read operation, streaming results have get/save/list but no delete, and file tools lack write/delete operations, leaving obvious lifecycle gaps.