Award Deep Dive
# Award Deep Dive
## User Input
- **Target award:** [Contract number, PIID, order number, GovTribe link, or award title plus agency]
## Goal
Use GovTribe MCP tools to resolve a specific federal contract award, task order, BPA call, or IDV-linked order and produce a grounded record-level brief.
Summarize the key contract facts, trace the award back to the originating notice when possible, surface the most useful government files, and explain modification or lifecycle evidence.
Focus on exact record resolution and supporting evidence, not broad market speculation.
## Required Documentation
Before doing any work, call the **GovTribe Documentation** tool and read the documentation required for this workflow.
Required documentation to retrieve and read:
- `article_name="Search_Query_Guide"`
- `article_name="Search_Mode_Guide"`
- `article_name="Search_Federal_Contract_Awards_Tool"`
- `article_name="Search_Government_Files_Tool"`
- `article_name="Search_Federal_Transactions_Tool"`
Retrieve these additional documentation articles only when the workflow needs them:
- `article_name="Search_Federal_Contract_Opportunities_Tool"` for originating-notice trace resolution
- `article_name="Search_Vendors_Tool"` for awardee identity normalization
- `article_name="Search_Federal_Contract_IDVs_Tool"` for parent-IDV lineage
- `article_name="Search_Federal_Contract_Vehicles_Tool"` for vehicle-level lineage
- `article_name="Vector_Store_Content_Retrieval_Guide"` only if file snippets are not enough and the user explicitly needs deeper document content
Documentation rules:
- Call the **GovTribe Documentation** tool before the first research or search step.
- Read every required documentation article before using other GovTribe tools.
- Follow the documented tool contracts exactly.
- Treat the documentation as binding for tool names, parameters, field definitions, relationship fields, sort keys, and valid output assumptions.
## Required Input
The user must provide a specific target award before analysis begins.
Accept any of the following:
- Contract number or PIID
- Order number
- GovTribe link
- Award title plus agency
- Plain-language description only if it is specific enough to resolve a single award
Optional constraints the user may provide:
- Whether to include the originating notice or related government files
- Whether to include transaction or modification history
- Whether to include parent vehicle or IDV lineage
- Whether the user wants a short **Award Card** or a fuller due-diligence view
Input rules:
- If the input resolves cleanly to one target, proceed immediately.
- If the input is too vague to resolve a single award, ask for the minimum missing detail needed to proceed.
- Do not guess the target.
- Do not start substantive analysis until the target is resolved.
## Workflow
### Rules
- Call `Documentation` before using any other GovTribe MCP tool.
- Contract-award-first only; do not mix in grant workflows.
- Use GovTribe MCP tools as the primary evidence in this workflow.
- Always set both `search_mode` and `query` on every `Search_*` call.
- Prefer exact lookup before broader recovery attempts.
- Use `query: ""` for filter-defined or ID-defined cohorts.
- Use `fields_to_return` whenever you need more than `govtribe_id`.
- Do not stop early when another tool call is required by the workflow.
- Keep calling tools until the task is complete or the tool budget is reached.
- If a tool returns empty or partial results and the workflow defines another defensible strategy, continue with that next strategy.
- Do not treat an absent `originating_federal_contract_opportunity` field as conclusive if the award, linked records, or parent lineage still provide a defensible path to search for the originating opportunity.
- Do not infer an originating notice, file trail, parent vehicle, or parent IDV unless the retrieved evidence supports it.
- Do not treat transaction rows as a substitute for award facts.
- Do not attempt competitor, customer-sentiment, teaming-preference, or shaping analysis in this workflow.
- Once you start a recovery branch such as originating-opportunity tracing, continue until you either confirm a defensible record or explicitly state that the available searches did not confirm one.
- Keep the workflow compact; add an extra tool call only when it materially improves correctness or grounding.
### Steps
1. Before doing any research, call `Documentation` and read every required article listed above.
- Add optional documentation articles only when their branch becomes necessary.
- Use the documentation results to confirm valid tool names, `search_mode`, `query`, `fields_to_return`, relationship fields, and sort keys before searching.
2. Resolve the target award with `Search_Federal_Contract_Awards`.
- Favor exact lookup first.
- For exact contract numbers, PIIDs, order numbers, quoted titles, or exact GovTribe-derived identifiers, use `search_mode: "keyword"` and a quoted `query`.
- If the user provides a GovTribe link, use the record identity embedded in the link when possible; otherwise resolve it through exact quoted lookup.
- If the user provides an award title plus agency, use the strongest exact title phrase plus agency context, then disambiguate with returned fields.
- Use `fields_to_return` explicitly. At minimum request:
- `govtribe_id`, `govtribe_url`, `govtribe_type`, `name`, `contract_number`, `award_date`, `completion_date`, `ultimate_completion_date`, `contract_type`, `descriptions`, `govtribe_ai_summary`, `dollars_obligated`, `ceiling_value`, `set_aside_type`, `awardee`, `parent_of_awardee`, `federal_contract_idv`, `federal_contract_vehicle`, `contracting_federal_agency`, `funding_federal_agency`, `naics_category`, `psc_category`, `place_of_performance`, `transaction_contacts`, `originating_federal_contract_opportunity`
- Use date sorting only when multiple historical variants or similarly numbered records need review.
3. If multiple awards match, disambiguate with the minimum additional evidence needed.
- Compare agency, awardee, award date, contract type, obligation size, and vehicle context.
- Do not merge multiple possible matches into one narrative.
- If the record still cannot be resolved to a single award, stop and ask for one clarifying detail.
4. If exact resolution fails and the user input is still specific enough, run one narrow recovery retry before asking for clarification.
- Broaden only one dimension at a time, such as title phrasing or agency context.
- If the retry still does not produce a single defensible match, stop and ask for the minimum missing detail.
5. Normalize awardee identity only when it materially improves the answer.
- If awardee identity, parent-child structure, or legal-entity naming matters, use `Search_Vendors`.
- Prefer `vendor_ids` from award relationships when available.
- If no vendor ID is available, use an exact quoted company name in `Search_Vendors.query` with `search_mode: "keyword"`.
- Request `govtribe_id`, `govtribe_url`, `name`, `uei`, `dba`, `parent_or_child`, `parent`, `business_types`, `sba_certifications`, and `govtribe_ai_summary`.
- Use vendor normalization to clarify identity, not to replace award evidence.
6. Trace the originating notice or opportunity when possible.
- If `originating_federal_contract_opportunity.govtribe_id` is already available from the award result, use it directly.
- If a `federal_meta_opportunity_id` is available from linked evidence or prior context, resolve it with `Search_Federal_Contract_Opportunities`.
- If the direct relationship is absent but the award still provides an exact identifier or strong context, run an independent opportunity search before concluding that no originating opportunity can be confirmed.
- Use this recovery order:
1. ID-defined lookup with `query: ""` plus `federal_contract_opportunity_ids` or `federal_meta_opportunity_ids` when those IDs are available.
2. Exact quoted `search_mode: "keyword"` lookup using the best available solicitation number, order number, contract number, or exact title phrase.
3. Retries that broaden only one dimension each, such as agency context or title phrasing, if the first independent lookup does not confirm a single defensible opportunity.
- If the award clearly sits under a linked IDV or vehicle and direct opportunity tracing still fails, use one targeted parent lookup early if that parent record may expose `originating_federal_contract_opportunity`.
- Use `search_mode: "keyword"` and `query: ""` when the opportunity cohort is fully defined by IDs or filters.
- Request opportunity fields only when needed:
- `govtribe_id`, `govtribe_url`, `solicitation_number`, `name`, `opportunity_type`, `posted_date`, `due_date`, `descriptions`, `govtribe_ai_summary`, `federal_meta_opportunity_id`, `federal_agency`, `government_files`, `points_of_contact`
- If more than one plausible opportunity is returned, disambiguate with agency, title, solicitation number, dates, file trail, and relationship context before concluding.
- Do not stop at intent, intermediate reasoning, or a partial retry. Finish this branch with either one confirmed originating opportunity or an explicit statement that the available searches did not confirm one.
- If no originating opportunity can be confirmed, say that clearly and do not infer a notice thread from loose keyword similarity.
7. Pull government attachments with `Search_Government_Files` only after an originating opportunity has been confirmed.
- Use `federal_contract_opportunity_ids` with the resolved opportunity GovTribe ID.
- Request `govtribe_id`, `govtribe_url`, `name`, `posted_date`, `content_snippet`, `download_url`, `parent_record`, and `govtribe_ai_summary`.
- Focus on files that materially explain the scope, amendments, Q&A, statements of work, attachments, or evaluation context.
- If no originating opportunity is confirmed, state that there is no confirmed opportunity-file trail.
8. Pull modification and lifecycle evidence with `Search_Federal_Transactions`.
- Use `query: ""`, `search_mode: "keyword"`, and the resolved `federal_contract_award_ids`.
- Request `govtribe_id`, `date`, `last_mod_number`, `reason_for_modification`, `total_value`, `federal_value`, `awardee`, `funding_federal_agency`, and `contracting_federal_agency`.
- Use `sort` with `transactionDate` descending.
- Treat transaction rows as supporting lifecycle evidence such as option exercises, funding increments, administrative changes, or other modifications.
- Do not infer option structure, extension status, or recompete timing unless the returned award or transaction evidence actually supports it.
9. If the award clearly sits under an IDV or vehicle and the user asked for lineage, run one targeted parent lookup.
- IDV path with `Search_Federal_Contract_IDVs`:
- Use the linked IDV when available, or an exact quoted contract number if that is all you have.
- Request `govtribe_id`, `govtribe_url`, `name`, `contract_number`, `award_date`, `last_date_to_order`, `contract_type`, `description`, `govtribe_ai_summary`, `ceiling_value`, `set_aside`, `multiple_or_single_award`, `awardee`, `parent_of_awardee`, `federal_contract_vehicle`, `contracting_federal_agency`, `funding_federal_agency`, `naics_category`, `psc_category`, `place_of_performance`, `task_orders`, `blanket_purchase_agreements`, and `originating_federal_contract_opportunity`
- Vehicle path with `Search_Federal_Contract_Vehicles`:
- Use the linked vehicle when available, or an exact quoted vehicle name if needed.
- Request `govtribe_id`, `govtribe_url`, `name`, `award_date`, `last_date_to_order`, `contract_type`, `descriptions`, `govtribe_ai_summary`, `set_aside_type`, `shared_ceiling`, `originating_federal_contract_opportunity`, `federal_agency`, and `federal_contract_awards`
- Do not call both parent tools unless the evidence requires both and the extra call materially improves correctness.
10. Escalate file-content retrieval only when it is clearly necessary.
- If `content_snippet` is not enough and the user explicitly needs deeper document grounding, call `Documentation` with `article_name="Vector_Store_Content_Retrieval_Guide"`, then use `Add_To_Vector_Store`, then `Search_Vector_Store`.
- State clearly when the originating notice, file trail, parent lineage, or lifecycle evidence cannot be confirmed from the retrieved record set.
## Tool Budget
Design the workflow to stay compact.
Typical path:
- 5 documentation calls
- 1 award lookup
- 0 to 1 vendor normalization call
- 0 to 1 opportunity resolution call
- 1 government files call
- 1 transactions call
- 0 to 1 parent IDV or vehicle call
Expected total:
- Typical: 8 to 10 calls
- High end: 12 to 13 calls
Avoid exceeding 15 calls unless an extra call materially changes correctness.
## Output Format
Use markdown tables for key facts, key files, and any multi-row modification history.
Do not use Mermaid charts in this workflow.
Return the answer in this order:
1. **Target Award Summary**
- Briefly explain how the award was resolved
2. **Key Contract Facts**
- Use a required 2-column markdown table for the key facts
- Include contract number, awardee, agencies, contract type, dates, dollars, set-aside, NAICS/PSC, place of performance, and any directly linked vehicle or IDV fields that were retrieved
3. **Originating Notice / Opportunity Trace**
- State the linked opportunity if confirmed
- If not confirmed, say that clearly
4. **Key Government Files**
- Use a compact markdown table
- Recommended columns: `File`, `Posted`, `Why It Matters`
5. **Modification and Lifecycle Notes**
- If more than one transaction or lifecycle event is surfaced, use a compact markdown table
- Recommended columns: `Date`, `Modification`, `Why It Matters`
- If only one event matters, a short prose note is fine
6. **Parent Vehicle or IDV Context**
- Include only if applicable and actually retrieved
7. **Risks, Gaps, or Unknowns**
- Briefly note identity ambiguity, missing file trail, sparse mod history, or other data limits
8. **Overall Confidence**
- State overall confidence and why
## Citation Rules
- Only cite sources retrieved in the current workflow.
- Never fabricate citations, URLs, IDs, or quote spans.
- Use exactly the citation format required by the host application.
- Attach citations to the specific claims they support, not only at the end.
## Grounding Rules
- Base claims only on provided context or GovTribe MCP tool outputs.
- If sources conflict, state the conflict explicitly and attribute each side.
- If the context is insufficient or irrelevant, narrow the answer or state that the goal cannot be fully completed from the available evidence.
- If a statement is an inference rather than a directly supported fact, label it as an inference.Last updated
Was this helpful?