Skip to main content
Glama

FindMyBids

Check if I'm ready to bid

check_readiness
Read-onlyIdempotent

Check whether the user's business (their FindMyBids business profile) is ready to bid.

Give ONE of: bid_id (a FindMyBids bid ID), url (link to any bid page or PDF, any state or private client),
or text (pasted bid text). For url/text, also pass state (two letters), level ("federal"/"state"/"local"/
"private") and due_date (ISO) if known.
Returns a verdict, each requirement with status gap / check / ready / info, the sentence it came from,
walkthrough links for registration gaps, and an excerpt of the bid to confirm against.
Free accounts get 3 checks a month (shared with the website); Pro is unlimited.

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": "check_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
textNo
levelNo
stateNo
titleNo
bid_idNo
due_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world behavior, and the description adds real context beyond them: the quota model (3 checks/month on free accounts, shared with the website; unlimited on Pro), the verdict/status vocabulary returned, and that it draws on the user's existing business profile.

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?

Front-loaded purpose sentence, followed by compact input-mode rules, return summary, and quota note. Slightly dense with parentheticals and slash-separated enumerations, but every sentence adds information.

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?

With no output schema, the description still summarizes return values (verdict, per-requirement statuses, source sentence, walkthrough links, bid excerpt), which is what an agent needs to interpret results. Remaining gaps are minor: nothing about authentication requirements or error behavior when an ambiguous URL is combined with text.

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% across 7 parameters, so the description carries the burden and mostly does: it explains the three input modes, the two-letter state format, the level value set, and ISO due_date. Only the title parameter is left unexplained, and the 'one of' constraint on bid_id/url/text is stated.

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 and resource ('check whether the user's business ... is ready to bid') and scopes it to the FindMyBids business profile, which distinguishes it from siblings like get_bid, search_bids, or get_profile that fetch data rather than assess fit.

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?

Explicitly tells the agent to supply exactly one of bid_id, url, or text, and which supplementary fields to add for the url/text paths. It stops short of saying when to prefer this tool over alternatives such as get_bid or search_bids, but the input-selection guidance is unusually clear.

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