Skip to main content
Glama
Sign In

TenderCrest AI

by io.github.tendercrestai
OverviewDiscussionsAdmin

Read a SAM.gov opportunity

get_opportunity
Read-only

Read one SAM.gov opportunity by its notice URL or 32-character notice ID, including the notice description text when SAM.gov returns it. Descriptions are not complete solicitation packages; attachments are not imported. Free, no sign-in.

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": {
      "notice": "<notice>"
    },
    "name": "get_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
noticeYesSAM.gov notice URL or 32-character notice ID.

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 already mark it read-only, and the description adds useful context: it returns the notice description when available, excludes attachments, and requires no sign-in or payment. It does not cover error or rate-limit behavior, but this is solid extra disclosure for a simple read tool.

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?

Three short sentences, front-loaded with the action and identifier format; the limitations and auth/cost note are compact. No sentence is redundant or bloated.

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 single-parameter read tool with readOnlyHint and no output schema, the definition covers the identifier, what content is returned, and key exclusions. It could add a brief discovery alternative, but nothing critical for correct invocation is missing.

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 coverage is 100%, and the schema's notice parameter description already gives the URL/32-character ID format. The description repeats that accepted identifier form but adds no extra parameter constraints or formatting guidance beyond the schema.

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?

The description opens with a specific verb and resource, "Read one SAM.gov opportunity", and narrows the lookup to a notice URL or 32-character notice ID. It does not name or explicitly compare against sibling search_opportunities, so it stops short of full sibling differentiation.

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?

It implies use when a notice URL or ID is already known, and it warns that fetched descriptions are not complete solicitation packages and attachments are not imported. It does not explicitly tell the agent to use search_opportunities to discover notices or state when not to use this tool.

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