Skip to main content
Glama

Tenda

Add to pipeline

add_to_pipeline
Idempotent

Use this when the user wants to save a tender to their team's Tenda 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 Tenda 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNoThe Tenda workspace to use, by name, when the user is in more than one, e.g. "Northbridge Services".
more_referencesNoMore tenders to add at the same time, by the same kind of reference, when the user asks for several, e.g. "add the two best fits". Up to 4.
tender_referenceYesThe notice ID, procurement identifier, solicitation number or the buyer's own reference, e.g. "012345-2026" on Find a Tender, "WS4851234567" on CanadaBuys or "140D0427Q0879" on SAM.gov.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
addedNo
stageNo
tenderNo
summaryYes
tendersNo
workspaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources