Skip to main content
Glama

FindMyBids

Search open bids

search_bids
Read-onlyIdempotent

Search open bids (government contracts and RFPs) that FindMyBids tracks.

query: keywords, e.g. "roof repair", "janitorial", "IT help desk". Commas mean OR: "roofing, gutters".
states: two-letter codes where the work is, e.g. ["PA", "MD"].
level: "federal", "state", "local" or "private" (private = bids private companies posted on FindMyBids, plus
invitations the signed-in user saved).
naics: NAICS code prefixes, e.g. ["5617", "238"].
set_aside: text to match, e.g. "Small Business", "8(a)", "HUBZone", "WOSB", "SDVOSB".
due_after: ISO date; defaults to today (only bids still open).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
limitNo
naicsNo
queryNo
statesNo
due_afterNo
set_asideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: due_after defaults to today so only still-open bids are returned, and the private level includes private-company postings plus invitations the signed-in user saved. It does not explain limit behavior, result ordering, or pagination.

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

Conciseness5/5

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

The definition is front-loaded with the core purpose and then efficiently explains parameters without redundant wording. Every sentence contributes useful search semantics or defaults.

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?

For a seven-parameter search tool with no output schema and no schema descriptions, the definition covers nearly all invocation semantics needed to call it correctly. It is only incomplete around the limit parameter and around what a result set looks like or how large it can be.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does so for six of seven parameters with concrete examples and semantics such as comma-as-OR in query, two-letter state codes, NAICS prefixes, and set-aside text. The limit parameter is not described at all, leaving one meaningful gap.

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

Purpose4/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 open bids, explicitly government contracts and RFPs tracked by FindMyBids. It is clear enough to separate from single-bid lookup or saved-bid tools, but it does not explicitly name a sibling or state the distinction from get_my_bids.

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

Usage Guidelines3/5

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

Usage is implied by "Search open bids" and by the default due_after behavior limiting results to currently open bids. However, there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for looking up saved or previously tracked bids.

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.

Resources