Skip to main content
Glama

FindMyBids

Save my bid alert

save_alert

Save a bid search as the signed-in user's FindMyBids alert. New open bids that match it are emailed to the user and listed by get_my_bids. This saves to the user's account: call it only after the user confirms the keywords and states.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>",
      "states": "<states>"
    },
    "name": "save_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
statesYesTwo-letter US state codes where the user wants work, e.g. ["TX"].
keywordsYesWhat the user's business does, comma-separated, e.g. "janitorial, floor care".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write confined to the account. The description usefully adds the downstream effect (new matching open bids are emailed and listed by get_my_bids) and the confirmation gate. It does not say what happens if an identical alert already exists, whether it overwrites, or whether authentication is required beyond the 'signed-in user' phrasing.

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?

Three short sentences, front-loaded with what is saved and followed by the effect and the precondition. Nothing is wasted, though the consequence clause and the precondition could be merged slightly for tighter flow.

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 two-parameter write tool with no output schema, the description covers purpose, side effects, and the user-confirmation gate, which is enough to call it correctly. Remaining gaps are edge-case behavior (duplicate alerts, overwrite semantics) rather than blockers.

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% and both parameters carry format examples ('janitorial, floor care', ['TX']), so the schema does the heavy lifting. The description adds no format or constraint detail beyond what is already documented, so baseline 3 applies.

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 (save) and resource (a bid search as the signed-in user's FindMyBids alert), scoped to the user's own account. An agent can immediately tell this creates a persisted alert rather than a profile or an individual bid, so it is distinguishable from save_profile and add_private_bid.

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?

Provides an explicit precondition: call it only after the user confirms the keywords and states. It also names get_my_bids as the place where matches surface, giving retrieval context. It stops short of naming a search-then-save workflow alternative (e.g. search_bids), so no explicit when-to-use-instead routing.

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