Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bonfire_list_organizations

Read-only

List US state and local governments on the Bonfire eProcurement platform. Filter by state or name to locate a specific government's portal for bid opportunities.

Instructions

List US governments on the Bonfire (Euna) eProcurement platform — the directory for bonfire_search_opportunities (keyless). Bonfire hosts thousands of US state/local governments' open-bid portals, each with a keyless RSS feed. Filter the curated seed by state (2-letter) / query (case-insensitive name substring); limit(1..200)/offset. Output: { organizations:[{ org, name, state }] }. Feed a result's org to bonfire_search_opportunities. ★HONESTY: this is a CURATED, live-verified SEED of 187 US orgs — Bonfire has NO keyless org-list API (its authoritative directory is auth-gated, out of bounds), and Euna markets up to ~900 US orgs, so the seed is PARTIAL (disclosed in _meta); probe {slug}.bonfirehub.com/opportunities/rss to extend. totalAvailable = the exact filtered seed count. STATE-LEVEL bid feeds on open-data portals are NOT in this directory: TX TxDOT lettings, advertised and taking bids = socrata_query data.texas.gov qh8x-rm8r; IL CDB capital bids that are ANTICIPATED and NOT YET POSTED = socrata_query data.illinois.gov 6rb8-ntpm (~48 rows, not IL's full register). Map: resource samgov://data-map/state-local.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOrgs per page, 1..200, default 50.
queryNoCase-insensitive name substring filter (client-side), e.g. 'county', 'ISD'. Optional.
stateNo2-letter US state filter (client-side), e.g. 'TX', 'CA'. Optional.
offsetNo0-based offset; page with _meta.pagination.nextOffset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds substantial context: it is a curated, live-verified seed of 187 orgs, no keyless org-list API exists, the seed is partial and disclosed in _meta, and how to extend coverage. This goes far beyond the annotation flags and is honest about limitations.

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 longer than typical but every sentence carries weight: purpose, parameters, output structure, honesty note, and alternatives. The key purpose is front-loaded, and the additional detail is justified. A minor deduction for length that could be tightened without losing value.

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 complexity (no output schema, 4 params, rich ecosystem of siblings), this description covers everything an agent needs: output format, how to chain with bonfire_search_opportunities, data limitations, and alternative data sources. Nothing critical is missing.

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 parameters are fully documented in the schema. The description repeats the filter semantics but adds context like 'curated seed' and 'totalAvailable exact filtered seed count', which adds slight value. However, it does not meaningfully extend beyond the schema, so 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?

States a specific verb ('List'), resource ('US governments on the Bonfire (Euna) eProcurement platform'), and clearly distinguishes from the sibling bonfire_search_opportunities by framing itself as the directory. Also differentiates from socrata_query for state-level feeds, so an agent can confidently select this tool.

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?

Explicitly says to feed a result's 'org' to bonfire_search_opportunities, and warns what is NOT in the directory (state-level bid feeds) with concrete alternative tools (socrata_query). Provides clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools