Skip to main content
Glama

FindMyBids

My matching bids

get_my_bids
Read-onlyIdempotent

Open bids that match the user's saved FindMyBids alerts (the same list as My bids on findmybids.com), soonest deadline first. new_since_days: only bids posted in the last N days (e.g. 1 for today's new bids).

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

Input Schema

NameRequiredDescriptionDefault
new_since_daysNo

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 readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: results are scoped to the user's saved alerts and returned in deadline order, which an agent could not derive from the annotations. It omits pagination, result caps, and what an empty alert set does.

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?

Two compact sentences, front-loaded with purpose and ordering, followed by the one parameter that needs explanation. The website cross-reference is genuinely clarifying rather than filler; nothing 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?

For a one-optional-parameter, read-only, no-output-schema tool with full annotation coverage, the description supplies purpose, scoping, ordering, and the filter semantics. Only minor gaps remain around the null-default behavior and result-set size.

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 coverage is 0%, so the description carries the burden for the single parameter, and it does: new_since_days is defined as a recency window on posting date with a concrete example ('1 for today's new bids'). It does not state what the null default does (presumably no time filter), leaving that one behavior to inference.

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?

Specific verb-plus-resource: it returns open bids matching the user's saved FindMyBids alerts, with the 'same list as My bids on findmybids.com' anchor and a stated sort order (soonest deadline first). It does not explicitly contrast itself with the sibling search_bids, so an agent must infer the saved-alerts-vs-arbitrary-search distinction.

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?

The use case is implied by the 'saved FindMyBids alerts' framing, and the new_since_days example ('1 for today's new bids') hints at a polling/'what's new' pattern. There is no explicit when-to-use or when-to-prefer-search_bids guidance, so routing relies on inference from the anchor to the user's saved-alert list.

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