Skip to main content
Glama
govconapi

io.github.govconapi/govconapi

Official
by govconapi
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Get Price Benchmark

get_price_benchmark
Read-onlyIdempotent

Get percentile distribution of comparable contract values by NAICS and pricing type to establish market ranges for price negotiation.

Instructions

Get the percentile distribution of comparable contract VALUE for a NAICS, broken out by pricing type. A price-analysis / market-range read for the Negotiate stage, not a win predictor. Factual, not scored.

Bid & Proposal / Negotiate tool, Pro only. Pair with get_price_position to see where
YOUR specific value sits, or get_labor_rate_benchmark for the labor-cost input.

- naics: 6-digit code, required
- set_aside: exact code, e.g. "8A", "SBA", "SDVOSBC", "WOSB", "HZC", "NONE"
- psc: 1-4 alphanumeric Product/Service Code, finer scope than NAICS
- pricing_type: pin one, e.g. "FIRM FIXED PRICE", "TIME AND MATERIALS", a rarer
  pricing arrangement can surface as a raw, undecoded single-letter FPDS code
  (e.g. "J", "Y", "Z") instead of a readable name; that's passthrough source data,
  not an error
- agency: name / acronym / CGAC code, narrows the comparable set to that agency
- value_basis: current (default) | potential | obligated
- date_from/date_to: filters on the FPDS transaction's `action_date` (when a
  modification/closeout action was recorded), NOT the award date or period of
  performance, a years-old contract can appear as a "current" comparable via a
  recent action on it

IMPORTANT: pricing type shifts the median 8x-3000x within a NAICS, use the
per-pricing-type blocks (`pricing_types`), not `combined`, for a meaningful
comparable. `combined` is blended context only, not a real number to price against.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pscNo
naicsYes
agencyNo
date_toNo
date_fromNo
set_asideNo
value_basisNocurrent
pricing_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

Discloses that date filters operate on action_date, warns that a years-old contract can appear as 'current' via a recent action, and cautions that 'combined' is blended context only, not a real number. These are non-obvious behavioral nuances beyond the read-only annotation.

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?

The description is well-organized: a concise opening, a parameter bullet list, and a crucial IMPORTANT note. No filler or redundancy; each sentence earns its place.

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

Completeness5/5

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

Covers all necessary context for correct invocation: parameters, usage caveats, and tool alternatives. The output schema exists, so not describing return values is acceptable per rubric. The description is complete for an agent.

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

Parameters5/5

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

With zero schema description coverage, the tool-level description fully explains every parameter, including that pricing_type can be a raw single-letter code and value_basis defaults to 'current'. This completely compensates for the missing schema annotations.

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?

States a specific verb ('Get'), a clear resource ('percentile distribution of comparable contract VALUE for a NAICS'), and explicitly mentions the breakdown by pricing type. It also distinguishes from get_price_position and get_labor_rate_benchmark, making it unambiguous.

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

Usage Guidelines5/5

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

Provides explicit pairing guidance with get_price_position and get_labor_rate_benchmark, and the IMPORTANT note instructs when to use per-pricing-type blocks vs. combined, ensuring the agent selects the appropriate tool and mode.

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

This server cannot be installed

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/govconapi/govconapi-mcp'

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