binance-announcements-mcp
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 |
|---|---|
| fetch_latest_announcementsB | |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching Binance announcements, leaving no room for confusion or misselection.
The single tool name 'fetch_latest_announcements' follows a clear verb_noun pattern, and since there are no other tools, consistency is inherently perfect. No mixed conventions or deviations exist to evaluate.
A single tool is too few for a server named 'binance-announcements-mcp', which suggests a broader scope for handling announcements. While the tool covers fetching, obvious gaps like filtering, searching, or managing announcements are missing, making the set feel thin and incomplete for the domain.
The tool surface is severely incomplete for an announcements domain. It only provides fetch functionality, lacking essential operations such as filtering by date, searching for specific announcements, or accessing historical data. This will likely cause agent failures when more complex tasks are required.