Skip to main content
Glama
Sign In

TenderCrest AI

by io.github.tendercrestai
OverviewDiscussionsAdmin

Search SAM.gov opportunities

search_opportunities
Read-only

Search live SAM.gov federal opportunities from the past 364 days. Returns up to 25 notices per page with title, agency, deadline, NAICS, PSC, set-aside, and the canonical SAM.gov link. Federal notices only; no contract value bands are published. Free, no sign-in. Limited to 10 searches per day, shared with the web feed.

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

Input Schema

NameRequiredDescriptionDefault
pscNo4-character product service code.
pageNoResults page, 0 to 9. Default 0.
naicsNo6-digit NAICS code.
keywordNoKeyword search, up to 100 characters.
setAsideNoSet-aside type code, up to 12 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds substantive behavior beyond that: 25 results per page, the exact fields returned, federal-only coverage, absence of contract value data, no auth requirement, and a hard shared daily quota. It does not say what happens at the quota boundary or how results are ordered, which keeps it off a 5.

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?

Four short sentences, front-loaded with scope, then return payload, coverage limits, and access/quota constraints. No sentence is redundant and nothing is buried mid-paragraph.

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 usefully compensates by enumerating returned fields, and it covers quota and auth. Remaining gaps are minor: error behavior when the daily cap is hit and result ordering are unspecified.

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%, so every parameter (psc, page, naics, keyword, setAside) is already documented in the schema. The description adds only the indirect detail that pages hold up to 25 notices; it offers no extra guidance on filter combination or how filters interact, so the baseline 3 applies.

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 ('Search live SAM.gov federal opportunities') plus explicit scope ('past 364 days', 'Federal notices only'), which lets an agent distinguish this from a single-record fetch like get_opportunity. It stops short of naming the record-fetch sibling, so differentiation is inferential rather than stated.

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 rate cap ('10 searches per day, shared with the web feed') and the 'no contract value bands' limitation implicitly tell the agent to search sparingly and not to expect value data. However, there is no explicit when-to-use/when-not-to-use guidance relative to siblings such as get_opportunity or check_bid_fit, leaving the choice to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TenderCrest AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources