Evidence Checks

# Quick Evidence Check

## User Input
- **Question:** [Focused factual question such as: is the site visit mandatory?]
- **Target context:** [Optional GovTribe link, solicitation number, contract number, or record title]

## Goal
Use GovTribe MCP tools to answer one focused factual procurement question with source citations.
This workflow is for short checks such as due date, site visit, mandatory attendance, set-aside proof, incumbent, part number, NSN, quantity, bids received, amendment status, or where a source says something.
Return a concise answer with evidence; do not expand into a full deep dive unless the user asks.

## Required Input
The user must provide a focused factual question.
Target context is optional, but if the question cannot be resolved without it, ask for the minimum missing detail.

Input rules:
- Answer exactly the question asked before adding context.
- If the evidence is not found, say that it was not found in the retrieved sources.
- Do not guess dates, mandatory attendance, quantities, part numbers, NSNs, incumbent names, or source locations.

## Workflow

### Steps
1. Call `Documentation` once with `collections=["govtribe-for-agents"]`, `article_names=["Choose a search mode and write queries", "Manage search context", "Filter by related records and hierarchies", "Vector-store content retrieval", "Troubleshoot search results"]`, and `max_tokens=10000`.
   - Treat the returned guide articles as binding for exact lookup, file retrieval, vector-store retrieval, and troubleshooting.
   - Use each selected tool schema as the source of truth for exact arguments, fields, filters, relationship fields, sorts, and response shapes.
   - If the connected MCP client does not expose a named tool, use the closest available GovTribe record, file, or vector-search tool the client provides. If no equivalent tool is available, state that limitation in the caveat.

2. Resolve the smallest useful target.
   - Use `Search_GovTribe` if the record type is unclear.
   - Use the relevant typed search tool when the question clearly points to a federal opportunity, state/local opportunity, award, IDV, vehicle, vendor, file, saved search, pipeline, or automation.
   - Prefer exact quoted identifiers and tight filters over broad keyword searches.
   - If the question includes a file name or source-location request, search the record first, then retrieve files.

3. Retrieve only the evidence needed.
   - Use `Search_Government_Files` for solicitation files, amendments, Q&A, attachments, site visit notices, bid abstracts, forms, part-number lists, and pricing or quantity attachments.
   - If the resolved record includes attached `government_files`, search those file IDs or file names before broader file queries.
   - Use `Add_To_Vector_Store`, then `Search_Vector_Store`, only when snippets do not answer the focused question.
   - If file text, snippets, vector-store upload, or vector-store search are unavailable or unauthorized, stop at retrieved record summaries and file metadata, and say the fact was not directly verified in file text.
   - Stop after the answer is supported or after a reasonable targeted search shows the answer is not available in retrieved sources.

4. Answer with precision.
   - Start with `Yes`, `No`, the exact value, or `Not found in retrieved sources` when possible.
   - Include the source and a short explanation.
   - If evidence conflicts, state the conflict and identify each source.
   - If the answer is an inference, label it clearly.

## Output Format
Return the answer in this order:

1. **Answer**
   - One direct sentence answering the question.

2. **Evidence**
   - Use a compact markdown table.
   - Recommended columns: `Source`, `What It Says`, `Why It Answers the Question`.

3. **Caveat**
   - Include only if evidence is missing, ambiguous, conflicting, partial, or based on a narrow source set.

4. **Next Step**
   - Include only if another specific source, file, amendment, or clarifying detail is needed.

## Citation Rules
- Only cite sources retrieved in the current workflow.
- Never fabricate citations, URLs, IDs, dates, values, or quote spans.
- Use exactly the citation format required by the host application.
- Attach citations to the direct answer and each evidence row.

## 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, answer only the supported part or say that the fact was not found.
- If a statement is an inference rather than a directly supported fact, label it as an inference.