BuyICT MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUYICT_UX_TOKEN | Yes | UX-Token from request headers | |
| BUYICT_SESSION_ID | Yes | JSESSIONID from the Cookie header | |
| BUYICT_USER_TOKEN | Yes | X-UserToken from request headers | |
| BUYICT_GLIDE_NODE_ID | No | glide_node_id_for_js from the Cookie header | |
| BUYICT_VALK_SESSION_ID | No | VALK_SESSION_ID from the Cookie header | |
| BUYICT_GLIDE_USER_ROUTE | No | glide_user_route from the Cookie header |
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 |
|---|---|
| search_opportunitiesC | Search for procurement opportunities on BuyICT with optional filters |
| get_opportunity_detailsC | Get detailed information about a specific opportunity |
| list_marketplacesB | Get list of available marketplaces/procurement types |
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 3 tools
Each tool has a clearly distinct purpose: get_opportunity_details retrieves details for a specific opportunity, list_marketplaces provides available procurement types, and search_opportunities finds opportunities with filters. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern using snake_case: get_opportunity_details, list_marketplaces, and search_opportunities. The verbs (get, list, search) are appropriate and uniformly applied, creating a predictable naming convention.
With only 3 tools, the set feels thin for a procurement domain that might require more operations like creating or updating opportunities. While the tools cover basic retrieval and listing, the count is borderline minimal for the apparent scope of a procurement server.
The tool surface is significantly incomplete for a procurement domain. It lacks essential CRUD operations such as create_opportunity, update_opportunity, or delete_opportunity, and does not include tools for managing bids or submissions. This will likely cause agent failures in full procurement workflows.