Skip to main content
Glama

get_solicitation

Read-onlyIdempotent

Retrieve structured SAM.gov solicitation fields by notice ID or solicitation number, including title, deadline, set-aside, contacts, and attachments, to feed into further analysis tools.

Instructions

Retrieve a single SAM.gov solicitation's structured fields by notice ID (or, best-effort, by solicitation number). Returns title, solicitation number, type, NAICS, PSC, set-aside, place of performance, response deadline (with timezone), points of contact, description, and attachment download links. Deterministic, free — pulls from SAM.gov's public opportunity records. This is the entry point for a workflow: feed the returned fields into score_go_no_go, find_incumbents, or find_partners_near.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noticeIdNo32-character hex SAM.gov notice ID (the ID in a sam.gov/opp/<id>/view URL). Primary, most reliable input.
solicitationNumberNoSolicitation number (e.g. '140P6026Q0003'). Best-effort fallback — resolved via SAM.gov search; provide noticeId when you have it.
includeAttachmentsNoInclude attachment download links (default true). Set false to skip the extra lookup.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noticeIdYes
titleYes
solicitationNumberNo
typeNo
typeLabelNo
naicsCodeNo
naicsCodesNo
pscCodeNo
setAsideNo
responseDeadlineNo
responseTimeZoneNo
placeOfPerformanceNo
pointOfContactNo
postedDateNo
modifiedDateNo
archiveDateNo
cancelledNo
archivedNo
descriptionNo
linkNo
attachmentsNo
Behavior4/5

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

Adds behavioral context: 'Deterministic, free — pulls from SAM.gov's public opportunity records.' This complements the annotations (readOnlyHint, idempotentHint) with additional details like determinism and cost. No contradictions.

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?

Two sentences, front-loaded with core functionality, second sentence adds workflow context. Every sentence earns its place.

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?

Lists returned fields and attachment download links. Since output schema exists, return values are covered. Could mention requirement for at least one identifier, but with no required params, it's acceptable.

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%, so baseline is 3. Description summarizes the two key parameters (noticeId primary, solicitationNumber fallback) but adds no extra detail beyond the schema descriptions. Does not address includeAttachments.

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?

Description clearly states it retrieves a single SAM.gov solicitation by notice ID or solicitation number, lists returned fields, and positions itself as an entry point for a workflow with specific sibling tools. This differentiates it well from other tools.

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?

Explicitly says 'This is the entry point for a workflow' and names follow-up tools. Provides guidance on primary vs. fallback input (noticeId vs. solicitationNumber). Lacks explicit when-not-to-use, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smythmyke/govtoolspro-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server