Skip to main content
Glama

FindMyBids

Save a private bid invitation

add_private_bid
Idempotent

Save a private bid invitation the user received (from a general contractor, property owner, or any company) so it shows up in their own searches alongside public bids. Only the user can see it. Paste the invite text or give its link.

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": {
      "title": "<title>"
    },
    "name": "add_private_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
textNo
stateNo
titleYes
agencyNo
due_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare write, idempotent and non-destructive behavior, so the description's main value-add is the visibility scope: 'Only the user can see it' and that the record surfaces in their searches. It says nothing about whether the URL is fetched and parsed, how fields are validated or defaulted, or what duplicates do beyond the idempotent hint.

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 being saved and why, then privacy scope, then input mode. Nothing is redundant, though the parenthetical source list is slightly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a write tool with no output schema and zero schema-level parameter documentation, so the description carries the full burden, yet four of six fields are left unexplained, including the only required one. An agent can call it, but cannot confidently populate state, agency, or due_date without guessing.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, and the description only maps loosely to two of them ('text' and 'url'). The required 'title', plus 'state', 'agency' and 'due_date', get no meaning, format, or derivation guidance anywhere in the definition.

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?

States a specific verb and resource ('Save a private bid invitation') and scopes it by source ('from a general contractor, property owner, or any company') and effect ('shows up in their own searches alongside public bids'), which separates it from a public search tool. It does not name a sibling, but the public/private distinction is explicit enough to route correctly.

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?

Gives a clear trigger (the user received an invite) and two input modes ('Paste the invite text or give its link'), implying it is not for discovering public bids but for ingesting one the user already holds. No explicit exclusion or named alternative is offered, so it stops short of a full when/when-not statement.

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