Skip to main content
Glama
GovCon API MCP

GovCon API MCP

Official

Price a bid

price
Read-onlyIdempotent

Benchmark bid values, rank a proposed value against comparable federal contracts, and look up GSA labor or SCA/Davis-Bacon wage rates for cost analysis.

Instructions

Price evidence for a bid. (Pro) needs the Pro plan.

  • benchmark (Pro): the distribution of comparable contract values. naics (required), psc, agency, date_from, date_to, pricing_type (shorthand: FFP | T&M | CPFF | CPAF | LH), set_aside (code: 8A | SBA | SDVOSBC | WOSB | HZC | NONE), value_basis (current | potential | obligated)

  • position (Pro): where a value ranks against comparable contracts. naics and value (a string, e.g. "2200000"), required; same optional filters as benchmark

  • labor_rates: GSA CALC ceiling hourly rates. labor_category (required), match (contains | exact), education_level (HS | AA | BA | MA | PHD), min_experience, max_experience, naics, vendor, worksite, business_size, security_clearance

  • wage_rates: SCA or Davis-Bacon hourly rates for an occupation. classification (title words, e.g. "Electrician"), occupation_code (SCA 5-digit), type (SCA | DBA), state, wd_number; sort_by: base_rate | classification | wd_number. For one place, get the WD first and read its rates

  • wage_summary: the spread of those rates. classification or occupation_code, type, state

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": {
      "kind": "<kind>",
      "filters": "<filters>"
    },
    "name": "price"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
filtersYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds a crucial behavioral detail: '(Pro) needs the Pro plan,' indicating an access restriction. It does not add rate limits, output format, or other behavioral context beyond annotations, but the plan requirement is meaningful.

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 a well-organized bulleted list that front-loads the core purpose and the Pro plan note, then details each mode with nested bullets. Despite its length, every line adds necessary parameter or mode information, and the shorthand notation (FFP | T&M etc.) is efficient. No wasted words.

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?

Given the tool's complexity (five modes, many filters, a nested filters object, 0% schema coverage), the description covers all inputs, access requirements, and usage tips. With an output schema present, it needn't explain return values, so the definition is complete for calling the tool correctly.

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?

Schema description coverage is 0%—the filters object has no documented properties—so the description carries the full burden. It thoroughly documents each mode's required and optional parameters, including allowed values (e.g., pricing_type shorthand, set_aside codes), and provides a helpful tip for wage_rates. This is comprehensive compensation.

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 'Price evidence for a bid' with a clear verb and resource, and enumerates the five pricing modes (benchmark, position, labor_rates, wage_rates, wage_summary), each with a distinct purpose. However, it does not differentiate from sibling tools like market or search, leaving the agent to infer overall scope versus alternatives.

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 description explains what each mode does (e.g., benchmark gives distribution, position ranks a value, wage_rates gives SCA/Davis-Bacon rates), which implies when to use each mode, but it never states when to choose this tool over sibling tools or any exclusions. No explicit when/when-not guidance is provided.

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

Deploy Server

Other Tools