Tenda

可用工具

• search_tendersUse this to find public sector contracts to bid for in the UK, Canada, the United States, Germany, France and the rest of the EU: open tenders, frameworks and upcoming notices from any public buyer. Searches the user's own countries unless they name one; get_coverage lists every source and when it was last read. Answers give the total; pass nextCursor back as cursor for more. Not for past winners (use search_contract_awards) or jobs. Example: {"query":"school cleaning","region":"North West","closing_within_days":30}
• get_tender_detailsUse this when the user asks about one tender, framework or standing offer, by notice ID, buyer reference or from earlier results: the deadline, the portal to submit through, lots, value, conditions, award criteria and what the buyer wants, in plain English. It also reads the competition: who holds the work now, what the buyer paid before, how many bids it drew, and whether the tender is worth chasing. Not for finding tenders (use search_tenders). Example: {"tender_reference":"012345-2026"}
• search_contract_awardsUse this to find who won public contracts in the UK, Canada, the United States, Germany, France and the rest of the EU, what a buyer paid last time, and which contracts end soon and may be re-tendered. Searches the user's own countries unless they name one. Answers give the total, pass nextCursor back as cursor for more, and summarise says who won most across every match. Not for tenders open now (use search_tenders) or a public body's total spending. Example: {"buyer":"Leeds City Council","query":"cleaning","summarise":"supplier"}
• assess_tender_fitUse this when the user asks whether their business should bid for a public contract, or which open tenders suit them best. Compares the tender's conditions of participation (turnover, insurance levels, experience and certifications), location and lot sizes with the company's profile, and returns a fit score with reasons, likely disqualifiers and gaps. Omit tender_reference to rank the open tenders that suit the company. It does not predict or guarantee an award. Do not use for general business strategy or for private-sector sales leads.
• check_bid_readinessUse this when the user wants to know what they're missing before bidding, for one tender or in general: registrations, certifications, insurance, policies and each country's own documents, such as Cyber Essentials in the UK, SAM.gov registration in the US or the DUME in France. A general check follows the user's home country. Returns what is held, missing or expiring. It gives readiness guidance, not legal advice. Not for Companies House look-ups or tax questions. Example: {"tender_reference":"003344-2026","documents_held":["cyber_essentials","iso_9001"]}
• draft_bid_responseUse this when the user wants help writing part of a response to a public tender: a quality question answer, social value response, method statement, case study, company overview, cover letter or clarification question. Returns a drafting brief built from the tender's award criteria, word limits and the user's facts, so the draft answers what evaluators will score. Write the draft from the brief. Do not use for job applications, grant applications or private-sector sales proposals.
• review_bid_draftUse this when the user has a draft answer for a public tender and wants it checked before submission, the way an evaluator would: word limit, every part of the question answered, specific evidence, firm commitments, no unfinished placeholders or empty superlatives, and what the section type needs (mobilisation, KPIs, measurable social value). Returns checks plus the tender's scoring criteria and a 0 to 5 rubric to score it against. Do not use to write a new answer (use draft_bid_response).
• watch_tendersUse this when the user wants alerts for new tenders or upcoming notices that match a search, or for changes to one tender they follow (clarifications, new deadlines, the award). Saves a watch and gives its watchId: matches show in get_tender_updates and, with notify, in the workspace's Slack or Teams channels that get changes. Needs a Winquill account. Not for seeing the user's watches (use list_watches) or stopping one (use stop_watch). Example: {"query":"office cleaning","include_upcoming":true}
• list_watchesUse this when the user asks which Winquill watches they have, or to find the one to stop: each watch with its ID, what it watches for, its countries and whether it posts to Slack or Teams. Needs a Winquill account. Do not use for what the watches found (use get_tender_updates). Example: {}
• stop_watchUse this when the user wants to stop one of their Winquill watches, by the watchId that watch_tenders or list_watches gave. It finds nothing new after that; what it already found still shows in get_tender_updates. Needs a Winquill account. Example: {"watch_id":"wch_abc123"}
• get_tender_updatesUse this when the user asks what's new from their Winquill watches: new matching tenders, pipeline notices, deadline changes, clarifications, cancellations and awards. Without since, it gives the updates not shown before and marks them seen. Agents that check on a schedule pass since, the nextSince from the answer before: it reads what was recorded after it, oldest first, and marks nothing. watch_id keeps to one watch. Needs a Winquill account. Not for searching (use search_tenders). Example: {"since":"eyJzZXEiOjQyfQ"}
• add_tender_documentsUse this when the user shares text from a tender's documents, or wants Winquill 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 Winquill'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}
• save_company_profileUse this when the user wants Winquill 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 Winquill account. Not for personal profiles or CVs. Example: {"summary":"Office and school cleaning in Greater Manchester","company_number":"08123456"}
• get_pipeline_statusUse this when the user asks how their team's bids are going, for a status report, or what is due: how many tenders are in each stage of their Winquill pipeline, which bids are running with their next step and due date, which tenders still need the bid or no-bid call, and which bids are waiting on a result. Needs a Winquill account and workspace. Do not use to find new tenders (use search_tenders) or for alerts from saved watches (use get_tender_updates).
• add_to_pipelineUse this when the user wants to save a tender to their team's pipeline to consider bidding, e.g. "add this to our pipeline" or "let's track the Falkirk cleaning framework". Adds it in Watching, ready for the bid or no-bid call, and says which e-tendering portal the tender is run on. Until the team has said whether it has an account on that portal, the answer asks; pass the question on, and record the reply with record_portal_account. Needs a Winquill account and workspace. Do not use for alerts about new tenders (use watch_tenders) or to record a decision to bid (use record_bid_call).
• record_portal_accountUse this when the user says whether their company has an account on the e-tendering portal a tender is run on, where suppliers get the tender pack and bid, often after Winquill asked as a tender joined the pipeline: "yes, we have an EU-Supply account" or "no, we're not on Atamis yet". Notes it for the whole team, so Winquill stops asking about that portal. Give the tender's reference, or the portal's name or the key Winquill gave (portal.key). Needs a Winquill account and workspace. Do not use to sign in to a portal: Winquill never handles portal passwords.
• record_bid_callUse this when the user's team has decided whether to bid: records the bid or no-bid call, the team's answers to Winquill'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 Winquill 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"}}
• update_bid_sprintUse this when the user says a step of a bid their team is running is done, or not done after all: decode the pack, assign questions, draft answers, review and score, final checks or submit. Ticks it off with who did it and when, and says what is next and when it is due. Ticking submit moves the tender to Submitted. Needs a Winquill account and a bid sprint, which starts with a call to bid (record_bid_call). Do not use to write or check answers (use draft_bid_response or review_bid_draft).
• assign_taskUse 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 Winquill 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"}
• move_in_pipelineUse this when the user wants to change where a tender stands in their team's Winquill pipeline: to Qualifying while they look into it, back to Watching, to Submitted, or to Won or Lost when the buyer announces the result. Moving to Bidding or No bid takes the bid or no-bid call (use record_bid_call). Needs a Winquill account and workspace. Do not use to take a tender off the pipeline (use remove_from_pipeline).
• remove_from_pipelineUse this when the user wants a tender taken off their team's Winquill pipeline, for good or until a change brings it back: "remove it until it gets a value". It deletes the tender's bid call, sprint and the files the team added; for one in Bidding, Submitted, Won or Lost the answer asks first, so confirm with the user and call again with confirmed. Needs a Winquill account and workspace. Not for moving a tender to another stage (use move_in_pipeline) or a no-bid call (use record_bid_call). Example: {"tender_reference":"012345-2026","return_when":"value"}
• choose_alertsUse this when the user wants to change which Slack and Teams channels get Winquill'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 Winquill account and workspace. Not for connecting a channel (Winquill dashboard, Settings, Connections) or for email alerts (use watch_tenders). Example: {"app":"slack","stop":["morning_summary"]}
• start_bid_draftUse this when the user wants Winquill 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 Winquill'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 Winquill. notify says where to hear when it's ready. Needs a Winquill account and workspace. Example: {"tender_reference":"012345-2026"}
• continue_bid_draftUse this to carry on a bid draft Winquill started with start_bid_draft: give it the buyer's questions it asked for, the team's answers to the questions Winquill asked, or the go-ahead to draft now with what it has (Winquill marks the gaps [TO CONFIRM]). Drafting starts once Winquill's questions are answered, or when draft_now is true. Pass each answer with the question's number or words. Needs a Winquill account. Do not use for a new bid (use start_bid_draft).
• get_bid_draftUse this when the user asks how a bid Winquill is drafting is going, or wants to read it: its progress in steps and answers written, each question with its word count and Winquill'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 Winquill. Needs a Winquill account. Example: {"tender_reference":"012345-2026"}
• rewrite_bid_answerUse this when the user wants Winquill to rewrite one answer in a bid it drafted, e.g. "make Q3 shorter" or "use the Glasgow contract as the example in 2.1". Winquill rewrites it in the background, marks it again and says when it's done. A bid's first ten rewrites are included; after that each uses a little of the workspace's allowance. Needs a Winquill account. Do not use before the draft is ready.
• add_winning_bidUse this when the user shares a bid their company won, for Winquill to learn from, e.g. after Winquill offers to learn from winning bids. Winquill keeps it in the workspace's Library and learns what worked in it (structure, tone, the evidence it uses) for the bids it drafts. Pass the bid's text as the user shared it, not a link. Needs a Winquill account and workspace. Do not use for the buyer's questions for a new bid (use start_bid_draft or continue_bid_draft).
• list_automationsUse this when the user asks what Winquill does on its own for their team: the workspace's automations, each with its rules as sentences, whether it's on and what it last did, and the ones Winquill suggests. Needs a Winquill account and workspace. Not for making one (use add_automation) or what one did (use get_automation_history).
• get_automation_libraryUse this when the user wants to know which automations Winquill can run for them, before making one with add_automation. Returns each one in Winquill's library, what it does and whether the workspace has it already. Needs a Winquill account and workspace.
• add_automationUse this when the user wants Winquill to do something on its own, again and again: add strong fits to the pipeline, remind people of sprint steps, check a bid before it closes, say what a buyer changed, or send a morning shortlist or a report. Makes one from the library, saved off. Read its rules back to the user; it runs only once turned on with turn_on_automation. Automations never submit a bid, write to a buyer or email anyone outside the team. Needs a Winquill account. Example: {"template":"morning_shortlist"}
• turn_on_automationUse this only after you have read an automation's rules back to the user in plain words and they said yes to turning it on. From then on it runs as the user, outside quiet hours, and acts on the team's pipeline as its rules say. Automations never submit a bid, send anything to a buyer, decline a tender, email anyone outside the team or change who is in the workspace. Needs a Winquill account; owners, admins and bid leads turn them on. Not for turning one off (use turn_off_automation).
• turn_off_automationUse this when the user wants one of the workspace's automations to stop. It stops running and keeps its rules and history, so it can be turned on again. Needs a Winquill account; owners, admins and bid leads turn them off.
• get_automation_historyUse this when the user asks what Winquill's automations did lately: the last 10 things they did, newest first, for one automation or all of them. Needs a Winquill account and workspace.
• share_tenderUse this when the user wants to share a tender or send someone its link. Returns a link anyone can open without signing in: it shows what the public notice says, and chat apps preview it with the tender's name, value and closing date. Give the link as it is. Nothing about the user or their workspace is in the link or on the page.
• get_coverageUse this to know where Winquill 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 Winquill reads, or to say how fresh results are. Not for searching (use search_tenders). Example: {"country":"Canada"}
• open_tendaOpens Winquill's own app from ChatGPT's sidebar: Today, the team's board, Find and each tender, with the bid call. The app moves between its pages itself.
• open_bid_panelOpens the team's live bids beside a chat: each bid's steps and questions, what scores, and a way to work on one in the chat.
• tenda_changesSays when the team's work in a workspace last changed, for Winquill's app to keep its page up to date.
• search_mentionsFinds the team's tenders and people by name, for @ mentions in ChatGPT.
• get_tenda_settingsUse this when the user asks which Winquill workspace ChatGPT uses, or which countries' tenders it shows: returns Winquill's settings in ChatGPT, the workspace (for someone in more than one) and the workspace's countries. Needs a Winquill account. Do not use for the company profile (use save_company_profile).
• update_tenda_settingsUse this when the user wants ChatGPT to use another of their Winquill workspaces, or to show tenders from another country or stop: set "workspace" to the workspace's name, or a country's key from get_tenda_settings (such as "us") to true or false. The workspace's home country stays on. Owners and admins change countries. Needs a Winquill account.
• set_up_tendaUse this when the user wants to set Winquill up for their company, or has just added Winquill and has no workspace yet: shows a short form in the chat for the company, where it works and the work it does, then how many open tenders fit it now. Needs a Winquill account. Do not use to change one fact the user names, such as a certification (use save_company_profile).
• find_companyFinds a UK company on Companies House by name, for Winquill's setup.
• finish_setupSaves what Winquill's setup was told, making the workspace for someone without one, and finds the open tenders that fit.

更新日期：2026-10-29（tools/list 实测）

配置到 Claude / Cursor

{
  "mcpServers": {
    "remote-ai-eshmere-tenda": {
      "type": "http",
      "url": "https://mcp.tenda.eshmere.ai/mcp"
    }
  }
}