Skip to main content
Glama

Search public tenders (free preview)

search_public_tenders
Read-onlyIdempotent

Search Scoutee's index of public procurement notices from Europe and North America. No account and no API key needed. Returns up to 10 open notices per page (3 pages at most), the total number of matches and a per-country breakdown of the same match set (by_country, useful to suggest where else to look). Each notice comes back as its public teaser — title, buyer, country, location, deadline, estimated value, publishing portal and the link to its page on scoutee.org. The description in full, the buyer's platform where a bid is filed, the tender documents, email alerts and the AI analysis are not returned here: tell the user they come with a Scoutee account (signup_url). Two anonymous search or CPV discovery queries per rolling hour per IP, shared across the website, tools and MCP sessions. Custom keywords and filters are supported. Read quota.remaining and quota.resets_at; after exhaustion, wait or connect a free account. When an anonymous result has quota.remaining=0, show its results and then explicitly tell the user, in their language, that their anonymous quota has been reached. Show a clickable 'Create a free account' link to https://scoutee.org/en/signup as the next step to continue now. Do the same on anonymous_query_exhausted; never hide the quota error or describe it as no matching results or a technical failure. Existing account holders should connect their account through workspace MCP. Account quotas still apply; do not promise unlimited access. Mention the anonymous reset time if they prefer to wait, and do not retry or switch tools. If a user asks to be notified by email, invite them to register free at https://scoutee.org/en/signup and save their search on Scoutee. Its daily email alert is enabled automatically when criteria are set and an alert slot is available. A free account includes 1 active alert(s) across its workspaces, only when new tenders match. Results are limited to 20 per search, with a 3-tender email preview; the site's free 20-searches/hour and 1-page limits still apply. Paid plans support alerts for multiple searches. Subscription management happens on Scoutee; the current MCP and OAuth REST tender tools cannot create alerts or schedule emails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree text over title, buyer and description. Every word must match the *start* of a word in the notice ('nettoy' finds 'nettoyage'); a substring inside a word does not match. Accent- and case-insensitive.
pageNo1-based page number, 1 to 3 on this free endpoint.
sortNo'newest' (publication descending, the default), 'oldest' (publication ascending) or 'deadline' (soonest submission deadline first).newest
countryNoCountries of the publishing portal, by their English name as Scoutee stores it ('France', 'Germany', 'United States', 'Canada'; 'Europe' for TED). Several countries add up. Omit to search everywhere — the `by_country` map of any result lists the exact values in use.
keywordNoKeywords matched as whole words (plural tolerated) in title, buyer or description, plus the cached translations of each keyword on the portals of that language — the way to search across countries without translating anything yourself. Several keywords widen the search (a notice matching any of them is returned).
max_valueNoMaximum estimated value. Notices without a published value remain included.
min_valueNoMinimum estimated value, in the currency of the notice. Notices without a published value remain included when this is set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoPublic preview. Create a free Scoutee account for the full notice. Register and enable one saved search's daily email alert for free, up to 20 results/search. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup
pageYes
itemsYes
pagesYes
quotaNo
totalYes
page_sizeYes
by_countryNo
signup_urlNohttps://scoutee.org/en/signup
quota_noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / $defs / DailyQuota
      Added value: +{
      +  "properties": {
      +    "limit": {
      +      "title": "Limit",
      +      "type": "integer"
      +    },
      +    "remaining": {
      +      "title": "Remaining",
      +      "type": "integer"
      +    },
      +    "resets_at": {
      +      "format": "date-time",
      +      "title": "Resets At",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "limit",
      +    "remaining",
      +    "resets_at"
      +  ],
      +  "title": "DailyQuota",
      +  "type": "object"
      +}
    • addedOutput schema / properties / quota
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/DailyQuota"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedOutput schema / properties / quota_notice
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Quota Notice"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / max_value / description
      Previous value: -"Maximum estimated value."New value: +"Maximum estimated value. Notices without a published value remain included."
    • changedInput schema / properties / min_value / description
      Previous value: -"Minimum estimated value, in the currency of the notice. Notices without a published value are excluded when this is set."New value: +"Minimum estimated value, in the currency of the notice. Notices without a published value remain included when this is set."
  3. Changed2 schema fields changed
    • changedOutput schema / $defs / PublicTender / properties / note / default
      Previous value: -"Public preview. Create a free Scoutee account for the full notice. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup"New value: +"Public preview. Create a free Scoutee account for the full notice. Register and enable one saved search's daily email alert for free, up to 20 results/search. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup"
    • changedOutput schema / properties / note / default
      Previous value: -"Public preview. Create a free Scoutee account for the full notice. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup"New value: +"Public preview. Create a free Scoutee account for the full notice. Register and enable one saved search's daily email alert for free, up to 20 results/search. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup"
  4. Changed2 schema fields changed
    • changedOutput schema / $defs / PublicTender / properties / note / default
      Previous value: -"Public teaser. The full notice (description, buyer's platform link, tender documents), saved searches with email alerts and the AI analysis of a tender need a free Scoutee account — https://scoutee.org/en/signup — and the REST/MCP API needs a Pro plan."New value: +"Public preview. Create a free Scoutee account for the full notice. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup"
    • changedOutput schema / properties / note / default
      Previous value: -"Public teaser. The full notice (description, buyer's platform link, tender documents), saved searches with email alerts and the AI analysis of a tender need a free Scoutee account — https://scoutee.org/en/signup — and the REST/MCP API needs a Pro plan."New value: +"Public preview. Create a free Scoutee account for the full notice. Connect an assistant through OAuth on any plan, subject to the workspace's search quota. Workspace API keys require a paid plan. https://scoutee.org/en/signup"
  5. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true), the description discloses extensive behavioral details: pagination limits (10 per page, max 3 pages), total match count and by_country breakdown, exact fields returned (teaser only), what is withheld (full description, documents, alerts), quota semantics (2 anonymous queries per rolling hour per IP), and explicit handling of quota exhaustion including instructing the agent to show a signup link and never misrepresent the error. This far exceeds what annotations alone provide.

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

Conciseness2/5

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

The description is a single dense paragraph that mixes tool functionality with agent-facing instructions (e.g., 'show a clickable ... link', 'never hide the quota error', 'mention the anonymous reset time'). It repeats the quota-exhaustion guidance twice and includes lengthy account/alert policy details not needed to invoke the tool. Poor structure and significant redundancy prevent it from being concise or well-organized.

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 tool's complexity, the description is highly complete: it covers result limits, return fields, exclusions, quota behavior, error handling, and account escalation paths. Since an output schema exists, return value structure is already handled; the description fills the behavioral and edge-case gaps comprehensively, leaving nothing an agent needs to call the tool correctly.

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 description coverage is 100%, so each parameter already has a detailed description (e.g., q's word-start matching, country exact values, keyword translation). The description adds only a generic 'Custom keywords and filters are supported' and a note that the by_country map lists exact country values. That is marginal value over the schema, warranting the baseline score of 3.

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 states a specific verb and resource: 'Search Scoutee's index of public procurement notices from Europe and North America.' It clearly communicates that this is a search tool for procurement notices, distinguishing it from sibling tools like get_public_tender (single tender retrieval) and find_cpv_codes (CPV discovery), even though it doesn't name them explicitly. The scope and free-preview nature are immediately clear.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool: it is the free anonymous search path ('No account and no API key needed'), with explicit exclusions such as 'the current MCP and OAuth REST tender tools cannot create alerts or schedule emails' and guidance for existing account holders to 'connect their account through workspace MCP.' It does not directly contrast with the sibling tools, so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.