Bidaya

Semantically search the organization's knowledge library (proposals, resumes, project sheets, and other firm documents). Returns contextually relevant excerpts grouped by knowledge file, with surrounding text for coherence and each file's summary and authored date. Use list_knowledge_tags for valid tag_slugs. limit is capped at 25. Not for live RFP opportunities — use search_opportunities for those.

search_knowledge

Semantically search the knowledge base for people, past projects, or partner companies.

search_entity

Report a problem with these Bidaya tools to the Bidaya team. Use it when a tool errors, returns wrong or incomplete data, behaves differently from its description, or lacks a capability you needed. Categories: BUG (error or wrong result), MISSING_DATA (expected organization data absent), CONFUSING_TOOL (description, parameters or output misled you), FEATURE_REQUEST, OTHER. Submit once per distinct problem, after you have finished working around it, and keep helping the user. Do not include secrets or credentials.

submit_feedback

Summarize the organization's pursuit pipeline. A pursuit is the workspace for one RFP the organization is pursuing. Its stage is QUALIFICATION, IN_PROGRESS, or SUBMITTED while open, then WON, LOST (with a lost reason), or NO_BID (No-Go: the firm decided not to bid, with a No-Go reason) once closed. Returns counts per stage, the win rate (WON / (WON + LOST); No-Go pursuits don't count), lost and No-Go reasons, pursuits closing within closing_soon_days, and past_closing: pursuits still in Qualification or In Progress after their closing date, which usually means the stage is out of date. outcomes_closed_from limits WON/LOST/NO_BID counts, the win rate, and lost and No-Go reasons to pursuits closed on or after that date; open stages are always current counts.

summarize_pursuits

Move pursuits to a stage on the pursuits board, or record how they ended. Changes what the user's whole team sees, so move only the pursuits the user asked about, and confirm with them first when you chose the pursuits yourself. QUALIFICATION, IN_PROGRESS, and SUBMITTED keep a pursuit open, reopening it if it was closed; WON, LOST, and NO_BID (No-Go) close it. lost_reason is required with LOST and only with LOST; no_go_reason is required with NO_BID and only with NO_BID. reason_note is what the reason was, in the user's words (at most 500 characters), required when the reason is OTHER and only then. Moving to SUBMITTED records today as the submission date; closing records today as the closed date; changing a Lost or No-Go pursuit's reason keeps its closed date. At most 50 pursuits per call. Pursuits already in the stage are listed in already_there; ones that can't be found or moved are listed in failed.

update_pursuit_stage

Fetch full content for a search result id (e.g. "kb-file:<uuid>", "person:<uuid>", "opportunity:<uuid>").

Get an opportunity's full detail: description, summary, per-source links (source_url, attachment urls), team views, linked project, and the org's recommendation for it when one exists.

List the organization's AI-generated opportunity recommendations, ordered by relevance (0..1) with the matching rationale and service areas. Dismissed recommendations are excluded. limit defaults to 20 (max 100); min_relevance_score filters out weaker matches.

Semantically search public RFP/tender opportunities aggregated from Canadian procurement portals. query must be at least 3 characters. A solicitation number or portal reference number (e.g. "IWS 2026-051", "00005195981") can be passed directly, alone or inside a longer query: exact matches are pinned first with matched_reference set to the number they matched. provinces takes two-letter codes (e.g. ["AB", "BC"]); date filters bound posting/closing dates. sort is relevance (default), closing_soonest, or posted_newest. Results include the org overlay: who on the team viewed each opportunity and any linked project. Use get_opportunity for full detail and source links.