Prozorro MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROZORRO_API_TOKEN | Yes | Your Bearer token for the Prozorro API | |
| PROZORRO_SERVICE_URL | Yes | Base URL for the API |
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_tendersC | Search for government tenders by EDRPOUCode code, legal name, or date range. |
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 searching for government tenders, making it distinct by default.
The single tool name 'search_tenders' follows a consistent verb_noun pattern. Since there are no other tools to compare, the naming is inherently consistent and predictable.
One tool is too few for a server focused on government tenders, as it suggests an incomplete surface. For this domain, typical operations like viewing tender details, submitting bids, or managing updates are missing, making the set feel thin and under-scoped.
The server has a significant gap in functionality for government tenders. While searching is covered, essential operations such as retrieving specific tender information, creating or updating tenders, and handling bid processes are absent, which will likely cause agent failures in real-world scenarios.