Skip to main content
Glama

FindMyBids

Get bid details

get_bid
Read-onlyIdempotent

Details for one bid. bid_id: a FindMyBids bid ID, e.g. "nj:27DPP01349". include_text=true also reads the bid page and main document and returns an excerpt.

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": {
      "bid_id": "<bid_id>"
    },
    "name": "get_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
bid_idYes
include_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine value beyond them: include_text=true triggers an additional read of the bid page and main document and returns an excerpt, which tells the agent this option costs an extra remote fetch and yields different output. No pagination, auth, or failure behavior is mentioned.

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?

Two short sentences, the purpose front-loaded and the optional-parameter behavior immediately after. Every clause carries information; the only nit is that the purpose sentence is a bare fragment that could state a verb ("Retrieves") for slightly faster parsing.

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 simple two-parameter read tool with no output schema, this is close to complete: both parameters are explained and the conditional extra-fetch behavior is disclosed. What remains unstated is the shape of the returned bid details (fields available) and what happens for an invalid or unknown bid_id.

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 both parameters, and it does: bid_id is identified as a FindMyBids bid ID with a concrete example format, and include_text is explained by its effect (extra fetch plus excerpt). It stops short of describing what the non-text response looks like or the size/content of the excerpt.

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?

"Details for one bid" names the resource (a single bid) and the retrieval intent, and the bid_id example ("nj:27DPP01349") makes it unmistakably a single-record lookup. It does not explicitly contrast itself with search_bids or get_my_bids, so an agent must infer the distinction from the required ID.

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

Usage Guidelines2/5

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

The description never states when to use this tool rather than search_bids (to find a bid) or get_my_bids (to list the caller's bids), nor any prerequisites. Usage is only implied by the fact that a single bid_id is required.

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