Skip to main content
Glama

govspendpulse

Monitor global government contracts and tenders across US federal, EU, UK, and development bank procurement databases. Query by keyword, agency, or region to find business opportunities.

Instructions

GovSpendPulse: Global government procurement intelligence API. 9 endpoints covering US federal contracts (USASpending.gov), active solicitations (SAM.gov), EU tenders (TED), UK contracts, global development bank opp

Coverage: Global

Endpoints: • us-contracts ($0.10): US federal contract awards • us-opportunities ($0.10): US active solicitations (SAM.gov) • eu-tenders ($0.10): EU procurement tenders (TED) • uk-contracts ($0.10): UK government contracts • global-opportunities ($0.10): Global procurement opportunities • agency-intel ($0.10): US agency spending intelligence • competitor-awards ($0.10): Competitor federal award analysis • development-bank ($0.10): Development bank procurement • contract-brief ($0.10): Full contract intelligence brief

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: us-contracts | us-opportunities | eu-tenders | uk-contracts | global-opportunities | agency-intel | competitor-awards | development-bank | contract-brief
langNoResponse language
keywordNoSearch term — e.g. cybersecurity, cloud computing, management consulting
naicsNoNAICS code — e.g. 541512 (computer systems design)
stateNoTwo-letter US state code — e.g. VA, CA, TX
year_fromNoFiscal year start — e.g. 2024, 2025
limitNoNumber of results (5, 10, or 20)
activeNoOnly return open solicitations
countryNoISO 2-letter country code — e.g. DE, FR, PL, NL (blank = all EU)
cpvNoCPV procurement code — e.g. 72000000 (IT services)
regionsNoComma-separated regions: australia, canada, asia, africa, latam, mena, un
agencyNoAgency name or abbreviation — e.g. DHS, VA, HHS, DoD, NASA, GSA
Behavior2/5

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

With no annotations provided, the description must convey behavioral traits. It mentions endpoints and pricing but fails to disclose key details like rate limits, side effects, authentication needs, or response behavior. The description is purely functional.

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 bullet points and front-loads the main purpose. It is reasonably concise given the number of endpoints, though some repetition could be trimmed.

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

Completeness3/5

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

Given no annotations and no output schema, the description provides endpoint names and basic purposes, which is adequate for endpoint selection. However, it lacks details on response formats, error handling, and usage limits, leaving gaps for a complete understanding.

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 the input schema already documents parameter semantics. The description adds some context via the endpoint list but does not enhance parameter meaning 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 'Global government procurement intelligence API' and lists 9 specific endpoints with brief descriptions. This distinguishes it from sibling tools, which cover different domains (e.g., cyberpulse, marketpulse).

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 makes the tool's domain clear (government procurement), providing implicit guidance for when to use vs. sibling tools. However, it does not explicitly state when not to use or list 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/GTCC777/pulsenetwork-mcp'

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