BigGo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIGGO_MCP_SERVER_REGION | No | Region for product search | TW |
| BIGGO_MCP_SERVER_CLIENT_ID | Yes | BigGo Client ID - Required for specification search | |
| BIGGO_MCP_SERVER_CLIENT_SECRET | Yes | BigGo Client Secret - Required for specification search |
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 |
|---|---|
| product_searchD | Product Search |
| price_history_with_urlD | Product Price History With URL |
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 clearly distinct purposes: one for product search and one for price history. There is no overlap or ambiguity.
Both tools use snake_case and are descriptive, but 'price_history_with_url' includes a preposition while 'product_search' is simpler, showing slight inconsistency in structure.
With only 2 tools, the server feels under-scoped for a product search domain, limiting its utility. Typically at least 3-5 tools are expected.
Missing essential tools like product detail, category listing, or filters. The surface only covers search and price history, leaving significant gaps.