Plugin tracker

Tools

Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.

Latest snapshot2026-09-12USmethodology registry-public-v1

Searchable tools

113,018

Authless tools

7,424

Auth required

100,766

Described tools

61,167

113,018 tools

get_conversationget · Full detail of one lead: LinkedIn profile info, status, and the complete conversation thread between the user's AI and the prospect ('us' = messages sent from the user's account, 'prospect' = their replies), plus any draft waiting for approval. ALWAYS read this before approving a pending message or replying to an escalated lead. Long threads are cut to the 100 most recent messages: when `truncated` is true the thread STARTS EARLIER than what you see (`total_messages` = the real count), so never conclude anything about how the conversation began.MimikFlowMimikFlowPluginrequiredSales & CRM
get_pipeline_settingsget · Read a campaign's fine-grained machine settings: reminder cadence (timing_* waits, timing_max_follow_ups, the selected offer-pitch follow-up, per-phase relance styles), first-message tone (cold_dm_formality tu/vous, style, length, emoji, CTA mode), setter tone (setter_style, setter_max_phrases), sending modes (cold_dm_mode / setter_mode: 'auto' sends by itself, 'semi_manual' queues every draft for the user's approval), sending days/hours per pipeline, daily/weekly volume caps, market/language settings, and the meeting follow-through (Suivi RDV) keys: nurture_pre_meeting / nurture_post_meeting (opt-in value messages before/after a booked meeting), meeting_reminder + meeting_noshow_recovery + meeting_cancel_recovery (live defaults, 'off' disables), and setter_post_booking (the AI answers booked prospects' simple questions, stays silent on thanks, escalates reschedules to the human). The meeting keys are the most often left untouched and the most valuable to set up: a reminder before the call and a message adapted to whether the prospect showed up are what turn booked calls into calls that happen, and `meeting_touches` can carry a media (a demo, a case study -- see list_media). Every empty value simply means MimikFlow's sensible default applies (these are tuning knobs, not required configuration). The keys are internal vocabulary: to the user, name each setting by what it does in their language ('le rythme des relances', 'le tutoiement du premier message'), never by its raw key. Read before updating with update_pipeline_settings.MimikFlowMimikFlowPluginrequiredSales & CRM
get_pipeline_statsget · The user's LinkedIn prospecting KPIs and funnel for a period: connection invites sent/accepted, first messages (cold DMs) sent, prospect replies, conversion goals reached (goal_reached = a won lead, usually a booked meeting), with per-step drop rates. Use it for recaps ('how is my prospecting going?') and to diagnose where the funnel leaks. A frequent leak: invites accepted but few replies, which usually means the first message's approach (formality, style, hook) does not fit the audience -- read real threads and the campaign profile, then tune the cold_dm_* settings. window is '7d', '30d' or 'lifetime'. Report the numbers to the user in plain words in their language (invitations envoyées / acceptées, premiers messages, réponses, objectifs atteints), never as raw field names.MimikFlowMimikFlowPluginrequiredSales & CRM
get_whatsapp_settingsget · Read one campaign's WhatsApp settings: the wording of the first message, the reminders and the AI that answers on this channel, its sending days/hours, plus the plan of messages around a booked meeting (see update_meeting_moments). What the campaign SAYS -- the offer, the target, the goal, the voice, the proof, the media library -- is shared with LinkedIn and is read with get_campaign_profile: only the channel's own wording lives here. An empty value means MimikFlow's default applies, which is a working configuration, never a gap. Name each setting to the user by what it does in their language, never by its key.MimikFlowMimikFlowPluginrequiredSales & CRM
get_win_loss_dataget · Raw material to coach the user on their sales conversations: full threads of recently WON leads (conversion goal reached) and LOST leads (dropped after the prospect had replied). YOU do the analysis: recurring objections, drop-off points, what worked in wins. Then translate EVERY finding into a concrete settings change (update_targeting for who gets contacted; update_campaign_profile for my_objections, the custom instructions, style or proof; update_pipeline_settings for the first-message tone when the opener does not fit the profiles contacted) and offer to apply it. Frame findings as settings to improve, never as defects of the product. outcome is 'won', 'lost' or 'both'.MimikFlowMimikFlowPluginrequiredSales & CRM
list_accountslist · The user's connected LinkedIn accounts. Most users have ONE; an AGENCE user runs several (e.g. one per client) from this single connector. Returns each account's id, name (label), LinkedIn plan, status (active/disconnected), how many campaigns run on it, and its lead-dedup pool (accounts sharing a non-empty pool never prospect the same people). Use this to know which accounts exist, then list_campaigns to see the campaigns of each, and target any campaign by its campaign_id -- one connector pilots every account.MimikFlowMimikFlowPluginrequiredSales & CRM
list_campaignslist · The user's prospecting campaigns. A campaign bundles one ideal customer profile (ICP) + one offer + one tone + its own leads and conversations; most users have one, agencies run several in parallel. Returns id, name, status (active/archived), lead count, and the LinkedIn account it runs on (linkedin_account_id + account_name -- an Agence user targets a client by picking that client's campaign). Optional `account_id` filters to one account's campaigns. When a tool gets no campaign_id it uses the primary (oldest active) one.MimikFlowMimikFlowPluginrequiredSales & CRM
list_escalationslist · Conversations MimikFlow's AI deliberately handed over to the human (status talk_to_human): the prospect asked something out of the AI's scope, requested a human, or a custom stop condition matched. The machine will NOT answer these; they wait for the user. Read each thread with get_conversation, then help the user craft an answer and send it via reply_to_lead. Covers every campaign by default (pass campaign_id to narrow to one client). total / has_more / next_offset describe escalation_cards; leads_waiting_total is the real number of prospects waiting for the user, of which the 30 most recent are listed.MimikFlowMimikFlowPluginrequiredSales & CRM
list_leadslist · List the user's prospects (leads found and worked by their automated LinkedIn prospecting). Filterable by status (comma-separated; 'connected' expands to every status where the LinkedIn relationship exists), tag name, or free-text search on name/position. Status meanings: new = found not yet contacted, connection_request = invite sent, connection_accepted = invite accepted, first_contact = first DM sent, discussion = the AI is talking with them, follow_up = being reminded, snoozed = re-engage at a future date, goal_reached = WON, talk_to_human = needs the user, dropped = abandoned. These codes are internal: report a status to the user in plain words in their language ('invitation envoyée', 'en discussion', 'objectif atteint'), never as the raw code. Paginated: `total` is the real number of matching prospects and `has_more` says whether you only saw a slice -- never present one page as the whole base, page with `next_offset` or narrow the filters.MimikFlowMimikFlowPluginrequiredSales & CRM
list_manual_conversationslist · LinkedIn conversations in the user's inbox that MimikFlow (the machine automating their LinkedIn prospecting 24/7) is NOT tracking: threads the user started or handled by hand, outside the automated pipeline. Scans the most recent chats and returns the untracked ones with the contact's name, headline and a chat_id. Use it when the user wants to see their manual conversations or hand one over to the machine; then call adopt_conversation with the chosen chat_id. Read-only: nothing is saved or contacted.MimikFlowMimikFlowPluginrequiredSales & CRM
list_medialist · The campaign's media library: the videos, documents, images and links MimikFlow can attach to a message. Each one carries a title, a description (what it is and when it is relevant) and, when the user set one, an explicit rule saying when the AI may send it. Use it whenever a conversation would land better with something to SHOW -- a demo video before a call, a case study after one, the document a prospect asked for -- and to get the `media_id` that attaches a file to a message around a booked meeting (update_meeting_moments). Most users upload one file and never wire it anywhere, so an unused media is worth mentioning once when their conversations show it would help. Files are uploaded in the app; this tool only reads what exists.MimikFlowMimikFlowPluginrequiredSales & CRM
list_meetingslist · Meetings the AI setter booked with prospects in the user's real calendar (the usual conversion goal). Returns prospect, datetime and status. upcoming_only=false includes past meetings. CAVEAT: only meetings stamped through a CONNECTED calendar appear here; a meeting agreed in conversation or self-booked via a link often does not. goal_reached in get_pipeline_stats is the source of truth for won leads -- never conclude 'no meetings booked' from this list alone.MimikFlowMimikFlowPluginrequiredSales & CRM
list_pending_messageslist · The user's approval inbox: messages MimikFlow's AI drafted for prospects but is holding until the user validates them (validation mode, or a coherence check flagged the draft). A processing item is visible but must not be acted on until MimikFlow finishes or asks for a calendar check. Workflow: read each lead's thread with get_conversation, then approve_pending_message (send as is), edit_and_approve_pending_message (improve then send), or reject_pending_message (never send). Covers every campaign by default (pass campaign_id to narrow to one client), oldest first, and paginated: `total` is the real backlog, `has_more` says a slice is missing -- page with `next_offset` before telling the user their inbox is empty or counting it.MimikFlowMimikFlowPluginrequiredSales & CRM
list_tagslist · List the user's lead tags (free labels used to segment prospects, e.g. by cohort, event or offer) with the number of leads carrying each. Tags are usable as a filter in list_leads. Complete list, never truncated.MimikFlowMimikFlowPluginrequiredSales & CRM
list_whatsapp_numberslist · The WhatsApp numbers connected to the user's MimikFlow, and what each one is allowed to do right now. WhatsApp is a second channel on the SAME prospects as LinkedIn: it answers people who write first (a wa.me link, an ad, a QR code), carries the messages around a booked call, fills and converts a live, re-activates an imported base, and can take over when LinkedIn goes silent. Read `quiet_reason` before telling the user anything is broken: a freshly connected number stays SILENT for 24 hours and then writes only a few messages a day for its first two weeks, on purpose. That is WhatsApp's own rule against numbers that behave like machines, not a malfunction and not something to work around -- explain it and say how long is left. `paused` means the number was put on hold automatically because too few of the conversations it opened got an answer; the fix is better targeting and a better first message, never more volume. Cold-outreach and reply ceilings, credits left and whether unknown senders are accepted are reported as they are: none of them is writable from here.MimikFlowMimikFlowPluginrequiredSales & CRM
reject_pending_messagereject · Reject a pending draft (it will never be sent). Setter drafts move the lead to talk_to_human, cold DM drafts drop the lead, follow-up drafts restore the previous status. Post-booking cards preserve the lead's current status. Also resolves escalation cards.MimikFlowMimikFlowPluginrequiredSales & CRM
reply_to_leadreply · Send one message to a prospect AS the user, in their existing conversation. Meant for conversations the AI handed over (talk_to_human) after reading the full thread with get_conversation, and for a quick courtesy message on a WON prospect right after a meeting ('merci pour ce call, je t'envoie un mail') -- a won prospect keeps its won status. Write in the conversation's language and the user's voice, and get the user's OK on the wording before sending: this message goes out immediately. SAFETY: the live LinkedIn thread is refreshed first, then the tool REFUSES to write when we already spoke last and the prospect has not answered since -- that is how a prospect the user answered by hand ends up reminded twice. The refusal returns the real last messages: read them, tell the user what is actually in the thread, and only pass allow_consecutive=true when they confirm they do want a second message in a row. channel: 'linkedin' (default) or 'whatsapp' when the prospect's number is connected and the conversation lives there. WhatsApp goes out under the number's own protections (daily ceiling, spacing, credits, opt-out): a refusal there is a safety rule doing its job, never a bug to work around.MimikFlowMimikFlowPluginrequiredSales & CRM
resolve_pending_calendar_outcomeresolve · After checking the real calendar for a draft marked calendar_outcome_unknown, record whether the meeting exists. This never sends a message. Use 'booked' only when the event is visible, otherwise use 'not_booked'. The draft then returns to normal review.MimikFlowMimikFlowPluginrequiredSales & CRM
resume_ai_on_leadresume · Give a conversation back to the AI. When MimikFlow (the machine automating the user's LinkedIn prospecting) hands a prospect over to the human -- the user answered by hand on LinkedIn, the AI escalated, or a reply landed while the AI was off -- that conversation stays manual forever: the AI stops answering and the reminders stop. This is the return path. It first syncs the real LinkedIn thread (so the messages the user typed by hand are recorded and stop being read as a new manual takeover), then puts the prospect back under the AI: it answers on its next run when the prospect spoke last, otherwise the reminder sequence resumes. The prospect's history and the notes the user wrote are kept, and the 'needs your attention' cards for that prospect are cleared. Only works on a prospect currently handled by the human. If the user answers by hand again afterwards, the conversation goes back to them, which is intended. Confirm with the user before calling: the AI will write to this prospect again.MimikFlowMimikFlowPluginrequiredSales & CRM
run_pipeline_nowrun · Trigger an immediate one-off run of a MimikFlow pipeline instead of waiting for its schedule (e.g. lead_scraper to go find prospects right now, connection_sender to send today's invites). All daily LinkedIn safety limits still apply, so 'now' never means 'more'. Not available for setter (it runs whenever a prospect replies) and tracking. To the user, describe the action in product words in their language ('je relance la recherche de prospects'), never with the internal pipeline id.MimikFlowMimikFlowPluginrequiredSales & CRM
search_conversationssearch · Full-text search across every prospect conversation (e.g. 'pricing', 'not interested', a competitor name). Returns matching leads with the matched snippets. Scans the 200 most recent matching messages only: `truncated` true means older matches exist beyond what is shown, so present the results as examples, never as an exhaustive count.MimikFlowMimikFlowPluginrequiredSales & CRM
search_helpsearch · MimikFlow's official help center content. Use it to answer ANY how-to or support question about MimikFlow (setup, features, plans, LinkedIn safety, billing, calendar, broadcasts, MCP...) with accurate product answers instead of guessing. Without arguments: the catalog of topics with their questions. With topic_id: that topic's full content. With query: every topic matching the text. Base your answer on this content and answer in the user's language.MimikFlowMimikFlowPluginrequiredSales & CRM
search_prospectssearch · Preview-search LinkedIn prospects matching a free-text query (e.g. 'expert comptable Bordeaux' or 'SaaS founder Paris hiring SDR'). Returns candidate profiles WITHOUT contacting or saving anything, marking those already in the campaign. Review with the user, then pass the chosen URLs to add_prospects_to_campaign.MimikFlowMimikFlowPluginrequiredSales & CRM
set_latest_updateset · Give the machine fresh news from the user (a new case study, a new result, a new offer detail). For the next 30 days, MimikFlow swaps ONE reminder per lead with a re-offer message built from this news, a strong way to revive silent prospects. Max 600 chars, strictly factual (the AI must never invent numbers). Empty text clears it.MimikFlowMimikFlowPluginrequiredSales & CRM
snooze_leadsnooze · Schedule a future re-engagement for a lead. Two uses: (1) the prospect asked to be re-contacted later ('come back next month') -- the lead is snoozed and MimikFlow wakes it at the date with one warm re-engagement message, then resumes its normal cadence; (2) after a meeting happened (lead already won / goal_reached) -- the lead KEEPS its won status and gets ONE follow-up at the date, with no automatic cadence after it. Pass the optional `note` to give the AI real context for that message (summary of the meeting or call, the offer made, the agreed next step): the follow-up will reference it naturally instead of shipping a generic re-engagement. callback_at is an ISO date clamped to 1-90 days from now; null cancels the schedule and clears the note.MimikFlowMimikFlowPluginrequiredSales & CRM
tag_leadstag · Attach a tag (free label used to segment prospects) to a list of leads, creating the tag if it does not exist yet. Idempotent: already-tagged leads are unaffected. Useful to mark a cohort before filtering or reporting on it later.MimikFlowMimikFlowPluginrequiredSales & CRM
toggle_pipelinetoggle · Turn one of MimikFlow's automated pipelines on or off for a campaign. The prospecting chain: lead_scraper ('la recherche de prospects', finds new prospects that match the ICP), connection_sender ('les demandes de connexion', sends LinkedIn invites), cold_dm_sender ('le premier message', first personalized message), follow_up ('les relances', spaced reminders), setter ('l'IA qui répond aux prospects'). Extra lead sources: engagement_scraper ('les réactions à tes posts', people who like/comment the user's posts), profile_views ('les visiteurs de profil'), invite_manager ('les invitations reçues'), first_degree_scanner ('tes relations de 1er degré', existing connections). These ids are tool-call vocabulary only: to the user, always name the step by its product name in their language, never by its id. Changes apply within minutes; use run_pipeline_now for an immediate run. Warn the user before turning OFF part of the chain: leads then pile up unprocessed at that step.MimikFlowMimikFlowPluginrequiredSales & CRM
update_campaign_profileupdate · Update the campaign's settings. Writable keys: who_am_i, my_product, my_objections (answers to common objections), sender_name, communication_style, style_examples, social_proof_stories, goal_type ('call' or 'link'), goal_link, goal_label, and the OPTIONAL behavior overrides custom_cold_dm_instructions / custom_follow_up_instructions / custom_setter_instructions plus setter_custom_stop_condition (extra hand-off situations). These overrides personalize MimikFlow's built-in behavior (which already varies reminders, respects a no, stops on silence); leaving them empty is a valid, normal state, so only propose filling one to address a SPECIFIC pattern seen in the user's own conversations. Read get_campaign_profile first, change only what the user validated, and APPEND to existing instructions rather than overwriting them unless the user asks. Present each change in plain words ('tes réponses aux objections'), never by raw key name.MimikFlowMimikFlowPluginrequiredSales & CRM
update_pipeline_settingsupdate · Update the machine's fine-grained settings (same keys as get_pipeline_settings): reminder cadence and count, the selected offer-pitch follow-up, per-phase relance styles, first-message and setter tone, sending days/hours, sending modes, market/language. `target_regions` narrows prospecting to provinces / states / cities INSIDE the chosen countries (free text the user writes their own way, comma-separated, e.g. 'Quebec, Montreal' on a Canada campaign); empty means the whole countries. The first message's BASE STYLE is one choice made of two mutually exclusive keys: cold_dm_template picks a ready-made style, cold_dm_custom_template is the user's own example message the AI imitates. Setting either one automatically clears the other (they are reported in `cleared`), because an example message left behind silently overrides the chosen style. Daily and weekly VOLUME limits are readable but NOT writable here: how much a LinkedIn account may send is a human decision taken in the app, never reshaped from a chat. Each key is validated. CAUTION on modes: 'semi_manual' means NOTHING is sent until the user approves each draft in the inbox -- a forgotten semi_manual silently freezes the whole machine, so only set it on an explicit request and remind the user to process the inbox. Confirm every change with the user before saving, describing each setting by what it does in plain words, never by its raw key.MimikFlowMimikFlowPluginrequiredSales & CRM
update_targetingupdate · Rewrite the campaign's ideal customer profile: my_target (who the machine should find and contact) and/or my_anti_target (who it must avoid). Write in the user's language, concrete and specific (roles, sectors, company size, geography, pains). MimikFlow's prospect finder and evaluators apply the new text on their very next run, so confirm the wording with the user before saving.MimikFlowMimikFlowPluginrequiredSales & CRM
Legalcode Analyzelegalcode · Analyze supported corpora with counts, rates, averages, groups, matrices, trends, and actor statistics. Read Discover source_profile first: analyticsStatus and analyticsCapabilities are executable truth for the jurisdiction and source. Use court_case for court-only analysis and case for the broad decision rollup. Analysis may require q or a positive narrowing filter for expensive case aggregates, actor analysis, and high-cardinality matrices. q and a body-text filter target the same text, so provide one. Use measure document_count rather than count. Request sourceRef samples only when the profile explicitly allows them; use Search with matching filters for representative documents otherwise.LegalcodeLegalcodePluginrequiredOperations
Legalcode Discoverlegalcode · Discover the exact Legalcode search contract before querying: source-owning jurisdictions, agreement-party scopes, named sources and scoped sourceCode values, supported fields, bounded facets, prefix-constrained facet values, analytics and relationship readiness, query syntax, costs, and examples. Use mode:"jurisdictions" for corpus owners; mode:"agreement_scopes" for treaty/agreement coverage; mode:"source_profile" with jurisdiction and sourceType for fields and capabilities; mode:"facets" or "facet_values" for stored filter values; and mode:"help" for workflows. Treat case as the broad decision rollup, court_case as confidently classified courts, and agency_decision as administrative, regulatory, or tribunal decisions. Never guess sourceCode or enum values.LegalcodeLegalcodePluginrequiredOperations
Legalcode Fetchlegalcode · Inspect one document using a sourceRef copied exactly from Search or Trace. mode:"metadata" returns document context and law-version status. mode:"excerpt" uses q or sectionRef for a targeted passage; supported structured references include Icelandic articles, Irish sections, EU articles, and Icelandic bill commentary sections. Prefer a returned downloadUrl for complete-document retrieval. mode:"full" is a cursor-paginated fallback only when a download is absent or unavailable; follow nextCursor until truncated is false. An official publisher URL is provenance metadata, not a text-retrieval instruction.LegalcodeLegalcodePluginrequiredOperations
Legalcode Searchlegalcode · Search ranked primary-source candidates and snippets. Choose one jurisdiction and one or more discovered sourceTypes: law (including regulations, narrowed by actType), case (broad decision rollup), court_case, agency_decision, guidance, agreement, pre_law, or patent. Prefer explicit identifier filters such as lawKey, CELEX, ELI, citation, or sourceCode for known instruments. q remains free text and never creates structured filters. Use quoted phrases or flat AND/OR; do not send raw SQL, fielded backend syntax, wildcards, or a language filter. Results include sourceRef and may include a signed downloadUrl; use Fetch for metadata or targeted excerpts and follow response nextAction guidance.LegalcodeLegalcodePluginrequiredOperations
Legalcode Tracelegalcode · Trace deterministic indexed relationships rather than ranked text matches. Supported families include cases_for_law, laws_for_case, cited_cases, citing_cases, pre_law_for_law, related_pre_law_flows, eea_incorporation_for_law, implementing_laws_for_eu_law, and eu_law_for_implementing_law. Start from a sourceRef or an exact law, case, citation, or legal-basis key. Short number/year keys require an explicit jurisdiction. Relationship availability and resolution coverage vary by source; inspect Discover source_profile/help before relying on an edge family. After a pre-law trace returns a flow, use Search resultLevel:"document" with its flowKey to enumerate attached documents.LegalcodeLegalcodePluginrequiredOperations
Pet initial data intakepet · Capture name, petType as cat or dog, birthdate, breedType, breed details, and sizeOfPet from the user's initial message. Infer petType from explicit wording, pronouns, or breed names when possible; only dogs and cats can be insured. If the user asks to insure any other animal, respond only that Panda does not allow that for now and currently supports only dogs and cats. Do not ask follow-up questions, do not collect details, and do not continue to quotation for unsupported animals. If the pet type is unclear, ask. For cats, collect catType as indoor or outdoor. Ask and verify whether breedType is pure, hybrid, or unknown. If breedType is pure, collect firstBreed. If breedType is hybrid, collect firstBreed and secondBreed. If breedType is unknown, do not ask for breed names and keep both breed fields null. Collect sizeOfPet as either 0-44cm or > 44cm. Extraction should be handled by the LLM, not by backend regex parsing. After all fields are collected, ask the user to verify the captured data before continuing. After the user confirms the captured details, call quotation-tool with the confirmed values.PANDA TierversicherungPANDA TierversicherungPluginnoneFinance
Purchase quotepurchase · Create a Panda purchase quote link when the user wants to continue, buy, purchase, or proceed with a chosen Panda package. Use this after the user has selected or confirmed a package or tariff name, billing period, and all required dog or cat details. Only call this for cats and dogs; Panda does not insure other animal types. If the package name, billing period, pet name, pet type, birth date, breed details, or pet size are missing, ask for the missing values before calling this tool. After the tool returns a link, respond to the user with the exact clickable link and tell them to click it to continue.PANDA TierversicherungPANDA TierversicherungPluginnoneFinance
Quotation toolquotation · Render the confirmed pet details in a quotation widget and show a simple Panda insurance price. Call this only after the user has confirmed all pet details. Only call this for cats and dogs; Panda does not insure other animal types. Pass the confirmed values using the Panda API payload shape: name, petType as CAT or DOG, birthDate as YYYY-MM-DD, and nested breed details with applicable catType, breedType, firstBreed, secondBreed, and sizeOfPet.PANDA TierversicherungPANDA TierversicherungPluginnoneFinance
check_contact_duplicatescheck · Check whether any existing address-book contacts share the given email, phone number, or IČ (Czech business ID). Call this BEFORE create_contact when you have contact info, and warn the user if matches are found so they can decide whether to proceed.WorkeWorkePluginrequiredOperations
check_inquiry_duplicatescheck · Check whether any existing inquiries share the given email or phone number. Call this BEFORE create_inquiry when you have contact info, and warn the user if matches are found so they can decide whether to proceed.WorkeWorkePluginrequiredOperations
find_by_czech_icfind · Look up a Czech company by IC (identification number) in the official ARES registry. Returns company name, address, IC, and DIC. Use this to pre-fill data before creating a contact with create_contact.WorkeWorkePluginrequiredOperations
find_entityfind · Find the job (zakázka), the vehicle, the stock item or the address-book contact a free-text description refers to — a street, a school name, a customer, a supplier's job number, words from the inquiry; a car model, a plate, the garage that services it; a material as a supplier spells it; a company, a person, an IČ, a phone number or an e-mail. Use it when the user names a thing by something other than its exact name, before list_contracts or list_contacts. Results are ranked candidates with evidence, not confirmed matches. Each result carries the evidence that matched — quote it when you tell the user which one you think they mean, and ask rather than assume when two candidates look alike. Response may include error="permission_denied" — relay that to the user, do NOT speculate about alternatives.WorkeWorkePluginrequiredOperations
get_calendar_eventget · Get full details of a single calendar event by ID, limited to calendars accessible to the current user (own + shared) — an event on a calendar they cannot access reads as not found.WorkeWorkePluginrequiredOperations
get_contactget · Get full details of a single contact from the address book by ID.WorkeWorkePluginrequiredOperations
get_contractget · Header data of one contract only — NOT costs, NOT profit, NOT invoicing: for "is it profitable", "how is it doing", "what did it cost" call get_contract_overview instead. Get full details of a single contract by ID — status, customer, owner (the salesperson responsible — obchodník), work teams, site address, planned/actual dates, price (omitted when the user may not view contract finances), closing/cancellation info, and the linked inquiry ID if the contract originated from one (use get_inquiry to fetch it). Use list_contracts first to resolve a contract name to its ID. For cost problems and warnings on the contract, follow up with get_contract_insights.WorkeWorkePluginrequiredOperations
get_contract_insightsget · Findings only, never a profitability answer: an empty list means no rule fired, not that the job is healthy — for costs, profit and margin call get_contract_overview. Get Worke Contract Insight findings for a given contract — issues the engine detected (cost over plan, unaccepted outbounds, overdue milestones, dormant contract, etc.). Each finding has a rule_code, severity (info/warning/critical), a translated title and message, source_type/source_id pointing at the offending row, and a payload with rule-specific context. Findings disappear automatically when the underlying condition is fixed — there is no separate "resolved" state. Response may include error="permission_denied" — relay that to the user, do NOT speculate about alternatives.WorkeWorkePluginrequiredOperations
get_contract_overviewget · One call, one answer about a contract (zakázka): header (status, customer, responsible salesperson, teams, site, dates), money (agreed price, invoiced so far, remaining), costs by kind (material, labor, subcontract, overhead) with labor hours and the biggest cost items, profit and margin. Pass the contract id, or the words the user used (a customer, a street, "Lipová 2. etapa") and it resolves them through the index. This is THE answer to "is it profitable", "how is it doing", "what did it cost" — prefer it over get_contract and get_contract_insights. Figures the user may not see are listed in caveats, not omitted silently. Response may include error="permission_denied" — relay it, do NOT speculate about alternatives.WorkeWorkePluginrequiredOperations
get_customer_overviewget · One call, one answer about a customer or supplier from the address book: the contact card, their contracts (status, salesperson, price), their inquiries (status, salesperson, converted or not), totals across their contracts (price, costs, profit, invoiced) and — when they also supply us — their documents of the last 12 months. Pass the contact id, or the name as the user said it (a surname, a company, an IČ, a phone) and it resolves it; when several contacts fit, the response carries disambiguation instead of guessing. Prefer this over list_contacts + list_contracts for any "what do we have with customer Y" question.WorkeWorkePluginrequiredOperations
get_inquiryget · Get full details of a single inquiry by ID: text, status and type (with labels), address, the responsible salesperson (owner), the subscribed colleagues and the contract it became, if any.WorkeWorkePluginrequiredOperations
get_inquiry_funnelget · The inquiry (poptávka) funnel over a period: how many were created in it, how many of those now sit in each status type by their current status (opened, confirmed, in_process, closed, rejected; "other" for a status of no known type), how many became contracts (counted apart from any status), and the same by month — for the whole company or for one salesperson. Answer "how many leads did we get / convert" from this, never by paging list_inquiries.WorkeWorkePluginrequiredOperations

Tool Explorer FAQ

What is Tool Explorer?

Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.

How do category and verb filters work?

Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.

Why do auth requirements matter?

Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.