Skip to main content
Glama
Sign In

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

searchGovernmentTenders

Live public sector procurement tenders (EU TED, UK Find a Tender, US SAM.gov), contract values, and submission deadlines. Use when discovering open public-sector RFP procurement tenders (EU TED, UK Find a Tender, US SAM.gov), estimated contract values in USD, CPV codes, and bid submission deadlines. Do not use for historical R&D grants or lobbying disclosures (use getLobbyingAndGovGrants).

Input Schema

NameRequiredDescriptionDefault
regionNoGeographic procurement portal filter (defaults to 'ALL').ALL
industry_keywordsYesProcurement sector keywords or 8-digit CPV code (e.g., 'cloud cybersecurity', 'medical imaging').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / industry_keywords / examples
      Added value: +[
+  "cloud cybersecurity"
+]
    • addedInput schema / properties / industry_keywords / minLength
      Added value: +3
    • addedInput schema / properties / region / default
      Added value: +"ALL"
    • addedInput schema / properties / region / enum
      Added value: +[
+  "ALL",
+  "EU",
+  "UK",
+  "US",
+  "CA",
+  "AU"
+]
    • addedInput schema / properties / region / examples
      Added value: +[
+  "EU"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / industry_keywords / description
      Previous value: -"Keywords or CPV code (e.g., cloud hosting, cybersecurity, medical supplies)"New value: +"Procurement sector keywords or 8-digit CPV code (e.g., 'cloud cybersecurity', 'medical imaging')."
    • changedInput schema / properties / region / description
      Previous value: -"Region or country filter (e.g., EU, UK, US)"New value: +"Geographic procurement portal filter (defaults to 'ALL')."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that data is 'live', which portals are covered, that values are in USD, and that CPV codes are accepted; however it says nothing about result volume, pagination, rate limits, or authentication, which matter for an agent planning a call.

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

Conciseness3/5

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

Front-loaded with the resource and sources, which is good, but the three sources 'EU TED, UK Find a Tender, US SAM.gov' are enumerated twice in consecutive sentences, and 'estimated contract values in USD' restates the first sentence. Roughly a third of the text is redundant.

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

Completeness4/5

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

Only two simple parameters with full schema coverage and no output schema, so the description need not explain return values. It covers scope, sources, currency, and the exclusion case; the remaining gap is operational behaviour (result caps/pagination) rather than anything structural.

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%, so the schema already documents both parameters including the enum and the keyword/CPV format. The description corroborates region coverage by naming the EU/UK/US portals and mentions CPV codes, but adds no syntax or behavioral detail beyond the schema — the baseline of 3 applies.

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?

Names the specific resource (live public-sector procurement tenders), the concrete sources (EU TED, UK Find a Tender, US SAM.gov) and what it returns (contract values, submission deadlines). It also explicitly distinguishes itself from the sibling getLobbyingAndGovGrants, so an agent can route without opening either schema.

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?

Contains both an explicit 'use when' trigger (discovering open public-sector RFP tenders, CPV codes, bid deadlines) and an explicit 'do not use for' exclusion that names the alternative tool. This is the full when/when-not/alternative pattern.

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

All mcp-livedatapro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources