"Step-by-step guide to breaking down a request into parts" matching MCP tools:

• how_to_get_startedA

  SkillfolioA

  Step-by-step guide to creating a Skillfolio profile, from resume upload to a published portfolio at skillfolio.studio/@your-handle.

  ConnectorNo auth

• postkey_guideA

  Postkey: Instagram DM Automation and Comment-to-DMA

  Postkey: Reads 1 to 3 topics of the Postkey guide, as markdown: how the parts work, step-by-step recipes, every plan's limits, the channels, approvals and the safety rules. Use it for how-to and rule questions, and after a refusal: most refusals name their guide_topic. For this profile's own state (what is connected, usage, what waits) use postkey_get_started instead. Changes nothing.

  ConnectorOAuth

• get_removal_routeA

  publicA

  For any of the 950+ sites in the takedown registry: the documented removal method (form, email, both, guide, or none), the opt-out URL and privacy email on record, the parent company that actually processes the request, sibling sites one request may cover, and a link to our step-by-step guide when one exists. Accepts a domain or a URL.

  ConnectorNo auth

• sixta_explain_planA

  sixta-connectA

  Turn raw EXPLAIN output into a plain-language diagnosis — no query needed. Paste PostgreSQL EXPLAIN / EXPLAIN ANALYZE (text or JSON) or MySQL EXPLAIN (tabular, \G, FORMAT=JSON, FORMAT=TREE) and get: what the planner is doing step by step, where the cost concentrates, named risk findings (full scans, spilling sorts, nested-loop blowups, row misestimates) with index suggestions, and what to look at next. Use when the user pastes EXPLAIN output or asks 'can you read this plan'. Input is analyzed in memory and never stored.

  ConnectorOAuth

• upload_design_fileA

  a2a2p — Agent-to-Agent-to-PhysicalA

  Turn local manufacturing file bytes into the temporary HTTPS reference used by specification.design_files. This is a bounded intake operation, not a request, provider call, quote, order, payment, or fabrication action. Common RFC 4648 transport forms are normalized, then decoded bytes are recognized by signature, checked against the declared format, screened before storage, retained for one hour, and never included in telemetry. Supported roles include geometry (STL/STEP) and drawings (DXF/PDF). The 2 MiB MCP ceiling is transport-specific; use POST /api/upload with purpose=manufacturing_design_file for files up to 8 MiB. Pass the returned file_reference object unchanged in specification.design_files on the next call.

  ConnectorNo auth

• dataset.buildA

  FlexOrch MCPA

  Package extracted records into a dataset for export (Step 4). Triggers an async dataset build from a completed execution. Returns a job_id immediately — poll with job.status until status='completed'. The completed response includes dataset_id, which you pass to dataset.export to retrieve all records as text. This step is required before calling dataset.export. Args: execution_id: Execution ID from a completed data_process job (from job.status or job.result). name: Dataset name. Auto-generated from the source filename if omitted. description: Optional description for this dataset.

  ConnectorNo auth

• explain_findingA

  MalinoisA

  Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.

  ConnectorNo auth

• parse_statementA

  financeA

  Parse a base64-encoded PDF bank/credit-card/loan statement and return the extracted fields WITHOUT saving anything. Premium-only. This is step 1 of a two-step flow: the extracted values are reviewed with the user, and a separate apply step writes the confirmed values to a specific account. Nothing is persisted by this tool. Args: pdf_base64: The PDF file encoded as a base64 string (<= 5 MB decoded). Image-only/scanned PDFs aren't supported. Returns: ``{"success": True, "fields": {...}, "fields_found": N, "account_type_hint": "credit_card"|"mortgage"|...|None}`` where each entry in ``fields`` is ``{"value": "1234.56", "confidence": 0.9, "source_text": "...", "source": "regex"}`` (the same shape the REST parse returns). The ``value`` strings are the inputs the apply step accepts. On failure: ``{"error": "..."}`` (not Premium, bad base64, not a PDF, too large, or unparseable).

  ConnectorAPI key

• set_exercise_noteA

  RepsA

  Use this when the user asks to add, change or clear their own note on an exercise, built-in or custom ("note on my bench: seat 4, pause on the chest"). The note is a short gym-floor cue the Reps app shows on the exercise and during a workout; a custom exercise's step-by-step how-to goes in `notes` on `update_custom_exercise` instead. Get the slug and the current `note` from `get_exercise_library`. `note` replaces the whole note (to add to it, send the old text plus the new); an empty `note` clears it. Applied at once, with no confirmation step, so use it when the user asks for the note or has just agreed to it, and say in one sentence what the note now says.

  Connector

  Destructive

  OAuth

• taskhold_createA

  TaskholdA

  File work for later: a bug, a refactor, a follow-up you aren't doing now (it lands in To Do). To file and start work at once, use taskhold_begin. Pass parent_task_id to add one step to an existing task (taskhold_plan for several). Returns the new id, status (todo) and priority. Fails if parent_task_id isn't found or is itself a step (steps don't nest), if project_id doesn't exist (pass project by name instead), or at the account's task ceiling.

  ConnectorNo auth

• venue_infoA

  UPFRONTA

  What to know before going to a venue, from UPFRONT's venue guide: the bag policy and what fans can bring, gates and entry, parking, getting there by transit or rideshare, and food and drink, including what the guide says about gluten-free, vegetarian or vegan, halal and kosher food. Matches questions like "what's the bag policy at MetLife?", "when do doors open at MSG?" or "where do I park for Lambeau?". venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field, Seattle"). topics: optional; only these parts, at more length: any of "bags", "entry", "parking", "transit", "food". Without it, every part. Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a guide for; for any other venue the answer says so and lists the ones with guides. Each part is the guide's own words ("text", plus the guide's "faq" questions and answers). factsLastChecked is the date UPFRONT last checked the guide's facts; rules can change for a single event, and the venue's own event page has the final word. guideUrl is the guide on UPFRONT. dietary lists what the guide says per diet; dietaryNotMentioned lists diets the guide doesn't cover, which doesn't mean the venue has nothing for them.

  ConnectorNo auth

• analyze_funnelA

  AIOProductOS MCPA

  Build a conversion funnel from the product's own events: distinct users per step, step-to-step conversion %, and drop-off, evaluated in the exact order you pass. Needs product-analytics events flowing; returns empty counts when none match. Pass `steps` as an ordered list of 2+ event names — call it with NO steps first to get the menu of available event names rather than guessing them. Optional product_id and window_days (default 30, valid 1–365). Pairs with analyze_paths to see where the drop-offs go.

  ConnectorNo auth

• redact_by_text_rangeA

  KDAN PDFA

  Redact PDF text by specifying the exact text to remove on each line. MANDATORY WORKFLOW — follow every step in order before calling this tool: Step 1 — Retrieve line text: Call list_redactable_line_text and note the exact 'text' string and 'line_index' for every line you intend to redact. Step 2 — Identify the text to redact: Provide the exact substring to remove. The value must appear verbatim in the line's 'text' field. - Non-CJK text (e.g. English): whole-word matching is enforced. "the" will NOT redact text inside "then", "there", or "either". - CJK text (e.g. Chinese): substring matching — "王大明" will match wherever it appears in the line. Step 3 — Build the content payload: Group redaction targets by page. Each page entry contains a list of { line_index, text } pairs. Example: content = [ { "page_index": 1, "lines": [ {"line_index": 3, "text": "John Doe"}, {"line_index": 7, "text": "confidential"} ] } ] Step 4 — Verify and re-redact if needed: After this tool returns, you MUST call list_redactable_line_text again with the NEW job_id to verify that all intended targets have been removed. If any target text still appears in the result, call redact_by_text_range again immediately with the remaining targets. Repeat until all targets are gone — do NOT report success until the verification confirms zero remaining targets. Creates a NEW job_id (with parent_job_id linking to the source). After redaction completes, call 'view_pdf' with the new job_id to display the result.

  ConnectorNo auth

• get_setup_statusA

  schedule-iiiA

  Answer "how do I get started?", "what do I do next?", or help a user who seems lost setting up. Returns where they are in the journey from an empty organization to a finished Schedule III statement, and the ONE next step to take. Call it WITHOUT client_id first (the organization view): it lists the entities this credential can see, or — if there are none — the step to create the first one. Then call it again WITH one entity’s client_id for that entity’s full step-by-step path (upload trial balance → confirm groupings → capture figures → generate → download). Each step has a status (done / next / todo / blocked / web_only) and either the exact tool to call or a web-app link. NARRATE ONE STEP AT A TIME — walk the user through the single `next` step; do not dump the whole list unprompted. Steps marked web_only are done in the Datavrn web app and need a login — never claim you can do them yourself. This tool reports STATUS only (counts, names, what is done) — it never returns a figure or balance; read those with get_statement_figures once a statement is generated.

  ConnectorNo auth

• run_gauntletA

  SHPBL: Repository Audit & RepairA

  One runner for an entire SHPBL repository audit and repair: survey, opening library comparison, evaluation, repair, the batched harvest, closing library comparison, the branded HTML report, and the write-back path. STRICT SEQUENCE: call it once with no `step` for the run card, then `step: 1`, `step: 2`, one step per turn, in order. Do the returned step, report one line to the person, then call the next. Never call two steps in one turn, never attempt the whole run at once, and never infer a finding you were not handed. From `step: 2` on you must pass `ledger_digest`; every 3 steps (adjustable with `checkpoint_interval`, max 10, only when the person asks for fewer pauses) the run pauses and you must ask the person before continuing, then pass `continue_ack: "continue"`. The final step hands over the report template and the write-back path. Your own model does all reading and writing. This full conductor requires a Practitioner key (7-day free trial). The free lane provides repository evaluation, not a partial or full gauntlet.

  ConnectorNo auth

• load_skillA

  AeviaA

  How this Aevia connection works, plus playbooks for results, reports, systems. Returns a skill's playbook as the result; takes no action itself. A playbook is step-by-step guidance for a multi-step job, too long for a description. `connector_guide` covers how this connection works: workspaces, refs, finding data, the library, building, calculating and failures. `assessment_interpretation` covers reading and comparing results: what an indicator result is and is not, a figure's anchors, functional-unit equivalence and comparison discipline. `report_writing` covers writing results up as a document, from a screening note to an ISO 14044 study. `product_system_authoring` covers building a new product system with `lca_compose_assembly` / `lca_compose_linked`: build order, which of the two fits, failure modes, and tagging life-cycle phases. A loaded playbook stays in context; one load per session suffices. Skills are gated on what the token can call; an unavailable request returns the available list.

  ConnectorAPI key

• accept_inviteA

  ctxstore — memory that follows you across modelsA

  Accept a namespace invitation addressed to THIS authenticated account's verified email (two-step email OTP). Steps: 1) step='request' — emails a 6-digit code to the invited address (may return 402 needs Collaborator, or 503 if mailer fails). 2) step='confirm' with code= the 6 digits — activates the grant. Then switch_workspace(name=<grantor>) enters it on this same connection (mcp_config with the X-Ctxstore-Workspace header is also returned for header-based clients). The code activates the named grant_id only; it authorizes nothing else. Obtain grant_id from list_invites(). Docs: https://ctxstore.ai/docs.html#verify-invitations

  ConnectorNo auth

• confirm-file-uploadA

  MemocoreA

  Step 2 of attaching a file: call this AFTER POSTing the bytes to the upload.url from request-file-upload. It verifies the object actually landed in storage and records it on the memo (file_id, name, type, size), returning the recorded file. Use the same memo_id and file_id you got from request-file-upload. Anyone with access to the memo can later download the file via a short-lived get-file-url link — there is no public/permanent link. Requires write access to the memo.

  ConnectorOAuth

• verify_supplier_listingA

  Reevol Source: supplier searchA

  Second step of request_supplier_listing: pass the requestId it returned and the 6-digit code from the email. Codes expire after 15 minutes and lock after 5 wrong tries (call resend_supplier_listing_code for a new one). On success the request enters the Reevol review queue.

  ConnectorNo auth

• launch_scenarioA

  MitigantA

  Run a multi-step attack chain against a cloud account connected to Mitigant. Returns the result if every step finishes within wait_seconds (default 20); a multi-step scenario usually takes longer, so expect it to return at once with the attackId and status RUNNING while it keeps running -- then poll get_attack_status with that attackId, and never launch it again (that would start a second scenario). This performs real actions on real cloud infrastructure, as several attacks in sequence -- it is not a simulation, and its blast radius is the combined blast radius of every step. Confirm with the user before calling: if their request could match more than one scenario in list_scenarios, show them the matching candidates with their names and descriptions and have them pick one -- don't guess which scenario they meant.

  Connector

  Destructive

  No auth

• build_depositA

  stakechainA

  Turns a chosen market into signed-ready calldata: an ordered list of transactions to deposit into it or leave it, across Morpho vaults, Aave reserves, Moonwell markets and this project's staking pools — three different protocol interfaces behind one call. The approve step is included only when the current allowance does not already cover the amount, read on-chain at request time. Use this once a market has been chosen and the decision is made. Use something else when: still choosing (`list_lending_vaults`, `best_yield`); weighing whether to go ahead (`market_profile`, `yield_history`). Nothing is signed or sent — the caller holds the keys. Simulate before sending. `amount: "all"` on a withdrawal exits by share rather than by figure, so interest accruing between the call and the block is not left behind.

  ConnectorNo auth