> ## Documentation Index > Fetch the complete documentation index at: https://docs.tendy.by/llms.txt > Use this file to discover all available pages before exploring further. # Tendy MCP Tools: Complete Reference for All 5 Tools > Complete reference for Tendy's five MCP tools: parameters, accepted values, and return shapes for every tool your AI assistant can call. The Tendy MCP server exposes five tools that your AI assistant can call to interact with your procurement data. Two tools cover discovery and detail retrieval (`search_tenders`, `get_tender`), two work with your saved search templates (`list_saved_searches`, `run_saved_search`), and one surfaces your bookmarked tenders (`list_saved_tenders`). All tools require an authenticated session — see [Connect](/integrations/mcp-connect) to set up credentials. *** ### search\_tenders Search Belarusian public-procurement tenders in the Tendy database by keyword, status, source, region, OKRB code, amount range, publish date, and urgency. Returns a compact, paginated list. #### Parameters A keyword, UUID, or external ID to search for. Leave empty to browse without a keyword filter. Filter by tender status. Accepted values: `active`, `closed`, `cancelled`. Pass multiple values to include more than one status. Limit results to one or more procurement platforms. Accepted values: `goszakupki`, `icetrade`, `butb`, `ppt_butb`. Filter by region using a substring match — for example, `Минск` returns tenders in the Minsk region and city. Filter by OKRB commodity code prefix — for example, `45.2` matches all construction-related codes under that branch. Filter by procedure type using a substring match. Return only tenders with a contract value at or above this amount. Return only tenders with a contract value at or below this amount. When `true`, include tenders that have no published contract value alongside priced results. Return tenders published on or after this date. Format: `YYYY-MM-DD`. Return tenders published on or before this date. Format: `YYYY-MM-DD`. When `true`, return only tenders whose deadline falls within the next 3 days. Page number for paginated results. Number of results per page. Maximum: `50`. #### Returns Total number of tenders matching the query across all pages. The current page number. The page size used for this request. Number of tender objects returned on this page. Array of compact tender objects. Each object includes: `id`, `external_id`, `title`, `amount`, `currency`, `deadline`, `status`, `source`, `region`, `company_name`, `procedure_type`, `published_at`, `url`. #### Example > "Find active IT-related tenders in Minsk published since 1 January 2025 with a value above 100,000 BYN, sorted by the most urgent deadlines." *** ### get\_tender Fetch the full details of a single tender by its Tendy UUID. Returns all available information: title, description, amount, deadline, procuring entity, OKRB codes, lots, documents, events, and requirements. #### Parameters The Tendy tender UUID. Obtain this from the `id` field in `search_tenders` results. #### Returns The full tender record including: Human-readable tender title. Full tender description and scope of work. Contract value. Currency code, e.g. `BYN`. Submission deadline in ISO 8601 format. Name of the procuring entity (contracting authority). Tax identification number (УНП) of the procuring entity. Name and contact details of the responsible officer. List of OKRB commodity classification codes attached to this tender. Individual lots, each with its own description, amount, and requirements. Attached procurement documents with download URLs. Timeline of key events such as publication, clarification deadlines, and award. Qualification and technical requirements for participating suppliers. #### Example > "Get the full details for the tender with id `3f2a1b4c-…`, including all attached documents and lot breakdowns." *** ### list\_saved\_searches List the authenticated user's saved search templates, including the filters stored in each template and how often Tendy notifies you of new matches. #### Parameters This tool requires no parameters. #### Returns Total number of saved searches in your account. Array of saved search objects. Each object includes: Unique identifier for the saved search. Pass this to `run_saved_search`. The label you gave the search when you saved it. The full set of filter parameters stored in this template. How often Tendy sends you email alerts for new matches — for example, `daily` or `instant`. ISO 8601 timestamp of when the search was saved. #### Example > "Show me all my saved searches so I can see which procurement categories I'm monitoring." *** ### run\_saved\_search Execute one of your saved search templates by its id and return matching tenders. Optionally override the page or page size to paginate through results. #### Parameters The saved search id. Retrieve available ids by calling `list_saved_searches` first. Page number to retrieve. Defaults to `1`. Number of results per page. Maximum: `50`. #### Returns Returns the same paginated tender list as `search_tenders`, applying the filters stored in the saved search template. #### Example > "Run my saved search called 'Road construction Grodno' and show me the latest matching tenders." *** ### list\_saved\_tenders List the tenders you have bookmarked in Tendy, returned in reverse chronological order so your most recently saved opportunities appear first. #### Parameters Page number to retrieve. Defaults to `1`. Number of bookmarked tenders per page. Maximum: `50`. #### Returns Current page number. Number of results on this page. Number of bookmarked tender objects returned on this page. Array of compact tender objects in the same format returned by `search_tenders`. #### Example > "List the tenders I've bookmarked so I can review the ones I flagged earlier this week."