Skip to main content
Glama
OjasKord

Tender MCP

by OjasKord

search_tenders

Search active government tenders from UK, EU, and US sources. Get AI-powered fit scores to decide whether to bid, investigate, or skip, preventing wasted resources on closed opportunities.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results per source (default 10, max 25)
keywordYesSearch keyword — company capability, product type, or service (e.g. "cybersecurity", "catering", "IT support")
sourcesNoWhich sources to search. Defaults to all three: ["uk","eu","us"]
days_oldNoOnly return tenders published in the last N days (default 30)
min_scoreNoOnly return tenders scoring above this threshold (default 50). Only applies when company_profile is provided.
company_profileNoDescription of the company capabilities and what contracts they are looking for. Used for AI fit scoring. More detail = better scores. If omitted, results are returned unscored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorsNo
keywordYes
scoringNoPresent only when company_profile was provided
tendersYes
checked_atYes
_disclaimerYes
total_foundYes
_intelligenceNoAlways-present upsell hook -- not gated by tier
sources_searchedYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full burden. It discloses the tool searches multiple sources simultaneously, returns a verdict with AI fit score and other fields, and warns about missed deadlines and wasted resources. It also provides workflow hints, ensuring transparency for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with the core purpose in the first sentence. It includes necessary usage guidelines and workflow hints, though it is slightly verbose with some redundancy. Overall, it earns its content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description need not detail return values, but it does mention key outputs (verdict, score, deadline, value, requirements). It also provides workflow context and consequences, making it complete for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter described. The description adds high-level workflow context but does not elaborate on individual parameters beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches active government tenders across UK, EU, and US. It uses specific verbs and resources, and distinguishes from the sibling tool 'get_tender_intelligence' by positioning it as the initial search step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('BEFORE your agent allocates proposal resources, drafts a bid response...') and provides context for its use in a procurement discovery workflow. It also advises calling 'get_tender_intelligence' next for scored tenders, offering clear guidance on alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OjasKord/tender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server