Tenda

Quality 69 / 100needs work

36 tools, about 14,995 tokens to load them all · tool set dc9c6b46e4f9 · tools last changed 2026-10-09 · checked 2026-10-20 11:08 UTC

Tool changes

• 2026-10-09get_coverageadded

  Use this to know where Tenda looks: the countries and sources it reads, how many open, upcoming and awarded notices each holds, and when each was last read. Use it before telling the user a tender isn't published anywhere Tenda reads, or to say how fresh results are. Not for searching (use search_tenders). Example: {"country":"Canada"}

• 2026-10-09rewrite_bid_answerchangedoutput schema
• 2026-10-09get_bid_draftchangeddescription, output schema
  before

  Use this when the user asks how a bid Tenda is drafting is going, or wants to read it: where it is, each question with its word count and Tenda's mark out of 5, what's left for the team to confirm, and the check of the whole bid. Give question to read that answer in full. Returns a link to the draft in Tenda, where the team edits it and downloads it in Word. Needs a Tenda account.

  after · 70% of words in common

  Use this when the user asks how a bid Tenda is drafting is going, or wants to read it: its progress in steps and answers written, each question with its word count and Tenda's mark out of 5, what's left for the team to confirm, and the check of the whole bid. Give question to read that answer in full. Once it's ready, it gives a Word file link that works for an hour, and a link to the draft in Tenda. Needs a Tenda account. Example: {"tender_reference":"012345-2026"}

• 2026-10-09continue_bid_draftchangedoutput schema
• 2026-10-09start_bid_draftchangeddescription, input schema, output schema
  before

  Use this when the user wants Tenda to write a whole bid for a tender for their team, e.g. "draft our bid for the Leeds cleaning tender". Tenda reads the buyer's questions, asks the team a few questions whose answers make the bid specific, then drafts every answer from the company's evidence in the background, marks each like an evaluator, checks the whole bid and revises its weakest answers. The team reads, edits and downloads it in Word in Tenda. Pass the buyer's questions, or the invitation to tender's text, in questions_text when the user has shared them, including the text of files they attached; otherwise Tenda reads documents the buyer published with the notice itself, or asks for them. Relay Tenda's questions to the user as they are. A whole bid uses one of the workspace's full bids for the month, so first call it without confirmed: Tenda starts nothing and says how many are left. Tell the user, and offer to write the bid here instead, answer by answer from draft_bid_response, which uses none. Call it again with confirmed set to true only once they choose Tenda's drafting. Needs a Tenda account and workspace. Do not use to write a single answer here (use draft_bid_response) or to check the user's own draft (use review_bid_draft).

  after · 52% of words in common

  Use this when the user wants Tenda to write a whole bid for their team: it asks a few questions, drafts every answer from the company's evidence, then marks and revises them. Relay Tenda's questions as they are. A whole bid uses one of the month's full bids, so first call it without confirmed, tell the user how many are left and offer to write it here with draft_bid_response, which uses none; call again with confirmed only if they choose Tenda. notify says where to hear when it's ready. Needs a Tenda account and workspace. Example: {"tender_reference":"012345-2026"}

• 2026-10-09choose_alertschangeddescription, input schemameaning changed
  before

  Use this when the user wants to change which of their team's Slack and Teams channels get Tenda's alerts, or asks where they go: "only send alerts to Teams", "stop the morning summary in Slack", "send new tenders to #bids too". The alerts are new tenders that fit the company (new_tenders), changes to tenders in the pipeline (changes), the weekday morning summary (morning_summary) and bid work nobody has yet (bid_work). Pick the channels by app, by a channel's name, or neither for every channel. send turns alerts on there and stop turns them off; with only set to true, every other channel also stops getting what was sent here. Change only what the user asked for: an app or channel they didn't mention keeps its alerts unless they said "only". With neither send nor stop, it changes nothing and says where alerts go now. A channel with no alerts stays connected, so the team can still ask Tenda there. Owners and admins can change alerts. Needs a Tenda account and workspace. `Do not use to connect or disconnect a channel, which is done in the Tenda dashboard (Settings, then Connections), or for alerts by email (use watch_tenders).

  after · 49% of words in common

  Use this when the user wants to change which Slack and Teams channels get Tenda's alerts, or asks where they go: "stop the morning summary in Slack". Change only what the user asked for; with neither send nor stop it changes nothing and says where alerts go now. Owners and admins can change alerts. Needs a Tenda account and workspace. Not for connecting a channel (Tenda dashboard, Settings, Connections) or for email alerts (use watch_tenders). Example: {"app":"slack","stop":["morning_summary"]}

• 2026-10-09assign_taskchangeddescription, input schema
  before

  Use this when the user wants to give work on one of their team's bids to someone, or take it on themselves: "give the Bristol bid call to Sam", "Priya can do the review on the NHS Lothian bid" or "I'll take the final checks". The work is the bid or no-bid call while a tender waits in Watching or Qualifying, or a step of its bid sprint, the next one unless the user names another. Says who has it now, and whether they heard in Slack. Owners, admins and bid leads give out work; anyone can take work their role can do. When the person's role can't do it, the answer says who can: ask the user before giving it to one of them. Someone not yet in the workspace is invited from Today in the Tenda dashboard. Needs a Tenda account and workspace. Do not use to tick a step off (use update_bid_sprint) or to record the bid call itself (use record_bid_call).

  after · 58% of words in common

  Use this when the user gives work on a team bid to someone, or takes it on: "give the Bristol bid call to Sam". The work is the bid call while a tender waits in Watching or Qualifying, or a sprint step, the next one unless named. Says who has it and whether they heard in Slack. When the person's role can't do it, the answer says who can: ask the user before choosing one. Needs a Tenda account and workspace. Not for ticking off a step (use update_bid_sprint) or the call itself (use record_bid_call). Example: {"tender_reference":"012345-2026","person":"Sam","task":"review"}

• 2026-10-09record_bid_callchangeddescription, input schema
  before

  Use this when the user's team has decided whether to bid on a tender: records the bid or no-bid call with the team's answers to Tenda's five questions (fit: is this work we do well; eligibility: do we meet every must-have; capacity: can we deliver it and write the bid in time; competition: can we beat the other bidders; value: is it worth winning) and the reason. A call to bid moves the tender to Bidding and plans a six-step bid sprint back from the deadline. Adds the tender to the pipeline first if it isn't there. Confirm the decision with the user before calling. Needs a Tenda account and a role that makes bid calls. Do not use to judge fit before the team decides (use assess_tender_fit).

  after · 57% of words in common

  Use this when the user's team has decided whether to bid: records the bid or no-bid call, the team's answers to Tenda's five questions and the reason. A bid moves the tender to Bidding and plans a six-step sprint back from the deadline; a tender not in the pipeline is added first. Confirm the decision with the user before calling. Needs a Tenda account and a role that makes bid calls. Not for judging fit before the call (use assess_tender_fit). Example: {"tender_reference":"012345-2026","decision":"bid","answers":{"fit":"yes"}}

• 2026-10-09save_company_profilechangeddescription
  before

  Use this when the user wants Tenda to remember their business for future searches, fit checks, readiness checks and drafting, or asks to set Tenda up from what you already know about their company. Fill in only facts about the company that the user has told you: what it does, its Companies House number (or a US company's UEI), size, staff, turnover, where it works, certifications and insurance. Leave out anything you are unsure of and any personal details about people. Show the user what you will save and let them confirm or correct it first. Saves to their Tenda workspace, which their team shares, and fills in more from Companies House (SAM.gov for a US company) and the public contracts the company has won. Needs a Tenda account. Do not use for personal profiles or CVs.

  after · 59% of words in common

  Use this when the user wants Tenda to remember their business for searches, fit and readiness checks and drafting. Fill in only company facts the user has told you, leaving out anything unsure and any personal details, and show the user what you'll save so they can confirm or correct it first. Saves to their team's workspace and fills in more from Companies House (SAM.gov for a US company) and contracts the company has won. Needs a Tenda account. Not for personal profiles or CVs. Example: {"summary":"Office and school cleaning in Greater Manchester","company_number":"08123456"}

• 2026-10-09add_tender_documentschangeddescription, input schema, output schema, annotationsmeaning changed
  before

  Use this when the user pastes or uploads text from a tender's documents (invitation to tender, selection questionnaire, specification or instructions to bidders) so Tenda can read the requirements the notice leaves out: minimum turnover, insurance levels, certifications, experience, references, site visits and TUPE. When the user is signed in, their later fit and readiness checks for that tender include them; signed out, Tenda keeps nothing and they count for this answer only. Pass the document text, not a file link. Do not use for documents unrelated to a tender.

  after · 33% of words in common

  Use this when the user shares text from a tender's documents, or wants Tenda to read the files the buyer published with the notice (read_published, signed in). Returns a checklist of everything the bid must include, each with its file, page and the buyer's own words, and the requirements the notice leaves out, such as turnover, insurance and certifications. When the workspace can use Tenda's AI, it also returns the questions the buyer scores and how they're marked. Not for documents unrelated to a tender. Example: {"tender_reference":"012345-2026","read_published":true}

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.