Remote MCP Server on Cloudflare
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherC | Get weather info for a given city. |
| get_current_dateB | 获取当前日期, 如果用户没有提供日期, 则返回当前日期, 如果用户提供的是相对单位, 如前天, 昨天, 明天, 则返回相对单位后的日期 |
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 2 tools
The two tools have completely distinct purposes: one handles date calculations and the other provides weather information. There is no overlap in functionality, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun naming pattern (get_current_date and get_current_weather). The structure is uniform and predictable, with no deviations in style or convention.
With only two tools, the server feels thin and under-scoped for a 'Remote MCP Server on Cloudflare', which implies broader capabilities. The tools are unrelated (date and weather), suggesting a lack of cohesive domain coverage.
The server's purpose is unclear from the toolset, but the two tools cover unrelated domains (date and weather) without any supporting operations. There are significant gaps, as neither domain has a complete lifecycle (e.g., no date formatting or historical weather), and the overall surface is severely incomplete for any coherent workflow.