Skip to main content
Glama
OjasKord

Tender MCP

by OjasKord

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
urlNoThe URL of the Tender MCP serverhttps://tender-mcp-production.up.railway.app

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

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_tendersA

Searches active government tenders across UK, EU, and US. Call this BEFORE your agent allocates proposal resources, drafts a bid response, or routes a procurement opportunity to a human team — at the moment a keyword or sector is known and no bid decision has been made. Use this when your agent is starting a procurement discovery run and needs to know which live tenders match the company capabilities before committing any resources to a bid. Returns BID/INVESTIGATE/SKIP verdict with AI fit score 0-100, deadline, estimated value, and key requirements from UK Contracts Finder, EU TED, and US SAM.gov simultaneously. A missed tender deadline cannot be recovered. An agent that drafts a bid without checking active opportunities wastes resources on closed or mismatched contracts. Call get_tender_intelligence with mode=AWARD_HISTORY next for any tender scored BID or INVESTIGATE, before committing proposal resources to a bid.

get_tender_intelligenceA

Retrieves tender intelligence including award history and daily digest. Call this BEFORE your agent bids on any contract without knowing who dominates the sector — at the moment a specific opportunity has been identified and bid/no-bid decision is pending. Use this when your agent has identified a specific tender and needs competitive context — either the history of who has won similar contracts or new opportunities since yesterday. AWARD_HISTORY: past contract winners for a keyword. DAILY_DIGEST: all new tenders last 24h for monitored keywords. Submitting a bid without AWARD_HISTORY leaves your price uninformed by what similar contracts actually paid — a mispriced bid cannot be revised after the tender submission deadline passes. Do not bid without running AWARD_HISTORY first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: search_tenders finds active tenders and provides an initial verdict, while get_tender_intelligence provides deeper competitive context on a specific tender. Their descriptions and usage guidance make disambiguation straightforward.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern with underscores (search_tenders, get_tender_intelligence), using clear verbs and nouns that reflect their functionality.

Tool Count4/5

With only 2 tools, the server is minimal but focused on core procurement discovery tasks. While slightly below the typical 3-15 range, the narrow scope justifies the small count.

Completeness3/5

The server covers search and intelligence gathering, which are critical early steps, but lacks tools for acting on tenders (e.g., bidding, tracking). This leaves the workflow incomplete for end-to-end procurement support.

Maintenance

ActivityMaintained
ResponsivenessNo issues