"A tool for following and completing a plan step by step" matching MCP tools:

• 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

• test_planner_triggerA

  agent4.ioA

  Dry-run the Dynamic Planner's escalation judge: would these messages be offered a step-by-step plan? Use it after editing the agent's `task`, since the task text is the **business-domain gate** — a vague task lets out-of-domain requests through, a narrow one turns real customers away. messages: the user's turns in order; the LAST one is treated as the current turn and the rest as that user's earlier messages (same window the live judge sees). samples>1 re-runs the judge to show stability (it is a probabilistic call). expect: pass true/false to get `matched`. Nothing is stored — no session, no enrollment. Tokens count toward the tenant quota (kind=planner). Returns {triggered, samples, goals[], domain, matched}. Reads the judge only: whether the user then ACCEPTS the offer is a separate, user-controlled step.

  ConnectorNo auth

• create_checkoutA

  eSIM TabbyA

  Start a purchase — the step after the user picks a plan from search_esim_plans. Call it with that plan's plan_id (get_plan_details shows the current price first). Returns an order_id and where to pay, on the rail you asked for: 'card' (the default) returns a checkout_url — a hosted Stripe page for a human to open in a browser; once they say they've paid, call get_order_status to confirm and carry on to the QR code. 'x402' returns an x402_url for a wallet to settle in USDC, with no browser step — only choose it if you actually hold a wallet. Never accepts payment details — a card is entered on the hosted page, and a wallet signs for itself. Calling it again for the same plan reuses the pending order (reused: true) instead of creating a duplicate.

  ConnectorNo auth

• aanet_depositA

  AANetA

  Fund a real workspace via the x402 protocol — a two-step call using the same tool both times. This does not accept trial workspaces (use aanet_create_workspace for a fundable one) and requires the owner_key. Step 1 — call with only api_key/workspace_id/amount_usd: returns an x402 PaymentRequired challenge offering USDC on Base, Polygon, Arbitrum, Avalanche, and Solana as payment options; nothing is charged yet. Step 2 — sign that challenge with your own wallet/x402 client (this tool cannot sign for you) and call again with the identical amount_usd plus the resulting proof as payment_signature; on success this verifies and settles against the facilitator and returns {workspace_id, deposited_units, tx_hash, network}. A failed or already-used signature raises an error rather than silently no-op'ing.

  ConnectorNo auth

• aanet_depositA

  Autonomous Agents Network (AANet)A

  Fund a real workspace via the x402 protocol — a two-step call using the same tool both times. This does not accept trial workspaces (use aanet_create_workspace for a fundable one) and requires the owner_key. Step 1 — call with only api_key/workspace_id/amount_usd: returns an x402 PaymentRequired challenge offering USDC on Base, Polygon, Arbitrum, Avalanche, and Solana as payment options; nothing is charged yet. Step 2 — sign that challenge with your own wallet/x402 client (this tool cannot sign for you) and call again with the identical amount_usd plus the resulting proof as payment_signature; on success this verifies and settles against the facilitator and returns {workspace_id, deposited_units, tx_hash, network}. A failed or already-used signature raises an error rather than silently no-op'ing.

  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

  financeB

  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

• 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

• search_problemsA

  Said It HereA

  Search SaidItHere for real-world software dilemmas, framework gotchas, tool fatigue, and battle-tested community consensus workarounds from Reddit, Hacker News, GitHub, and Stack Overflow. Usage Guidelines: - Primary discovery tool: use FIRST when investigating bugs, library gotchas, unexpected price hikes, or developer complaints by keywords. - Sibling routing: follow up with 'get_problem(slug)' using the discovered dilemma slug to inspect full evidence quotes, sources, and step-by-step workarounds. - Sibling routing: if 0 matching dilemmas are returned, use 'suggest_dilemma' to queue the topic for crawler consensus synthesis. - Do NOT use for generic language syntax lookups or textbook documentation queries. Behavior & Side Effects: - Pure read-only, safe, and idempotent query without side effects. Does not modify user, session, or database state.

  ConnectorNo auth

• microsoft_docs_fetchA

  Microsoft Learn MCPA

  Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.

  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

• get_tide_heightsA

  thirdtrailA

  Water height at a coastal point at a fixed step: a list of time and height_m pairs. Use it to plot a tide curve or read the height at a particular time; for just the highs and lows use get_tide_extremes. Metres relative to mean sea level, not chart datum. Defaults: from today, 2 days, and the finest step the plan allows, but no finer than 10m. Requires an API key on a paid Tides plan.

  ConnectorNo auth

• confirm_service_retirementA

  AnkraB

  Confirm a prepared retirement and DELETE the managed service and its data (step two of `ankra services delete`). The digest must be the one prepare_service_retirement returned: a plan that changed since, or that expired, is refused. This cannot be undone. Follow it with get_service_retirement until it settles. Requires applications.deploy and stacks.delete.

  Connector

  Destructive

  OAuth

• awareness_apply_skillA

  Awareness — Memory, Knowledge & Agent MarketsA

  Apply a learned skill — returns structured step-by-step execution plan. Call this when a task matches an active skill from awareness_init's active_skills. Returns the skill's methods, summary, and context-adapted guidance. Automatically marks the skill as used (resets decay timer). Args: skill_id: ID of the skill to apply (from active_skills). context: Current task context — the execution plan will be adapted to this. memory_id: Target memory id (auto-resolved if omitted). api_key: Bearer token for authentication.

  ConnectorNo auth

• clickd_log_workA

  mttrA

  Records a step of work on a site: what you planned, changed or checked, or where you got stuck. When: after each step, including one that carries out a proposal or a queued task. Instead: clickd_propose before deploying to a site set to approve; clickd_todo for tasks waiting. Inputs: `site` is a domain, like example.com. `step` is planned, changed, checked or stuck; `did` says what. `found`, `files` and `rules` (comma separated) add detail. `proposal` names the proposal carried out, `task` the queued task finished. Never send private data. Returns: kept, site, step and note, with proposal or task and left when given. Fails: a proposal or task not the person's keeps nothing and says so. Needs a person's key.

  ConnectorNo auth

• clickd_log_workA

  clickdA

  Records a step of work on a site: what you planned, changed or checked, or where you got stuck. When: after each step, including one that carries out a proposal or a queued task. Instead: clickd_propose before deploying to a site set to approve; clickd_todo for tasks waiting. Inputs: `site` is a domain, like example.com. `step` is planned, changed, checked or stuck; `did` says what. `found`, `files` and `rules` (comma separated) add detail. `proposal` names the proposal carried out, `task` the queued task finished. Never send private data. Returns: kept, site, step and note, with proposal or task and left when given. Fails: a proposal or task not the person's keeps nothing and says so. Needs a person's key.

  ConnectorNo auth

• configure_ad_stepA

  mcp-serverA

  Configure ONE step of an ad's setup wizard and save it. Saving a step never activates or publishes: the summary step is refused here — finish setup with activate_ad. Use this to set up an ad step by step IN ORDER, repeatedly targeting each step the previous result reported as nextStepType, until nextStepType is 'summary' (then call activate_ad). Identify the step by step_index (from get_ad steps[].index) — step_type alone targets the FIRST step of that type. Out-of-order calls return 'prerequisite_not_met' / 'step_not_available'. CONNECTION IS NOT CONFIGURABLE HERE: the connection/auth step (credentials, API keys, OAuth) can never be set through MCP. 'oauth_required' / 'credentials_in_ui' is TERMINAL — hand the returned oauthUrl or editUrl to the USER, then STOP and wait; do NOT resend the step, guess field codes or retry. Returns {integrationId, stepType, status, ready, lastStep, nextStepType, oauthUrl, transitions[], message}; status is 'saved', 'oauth_required', 'credentials_in_ui', 'prerequisite_not_met', 'step_not_available' or 'validation_failed'. A product export/generation and a deferred category-attribute download run ASYNC — poll ad_status (productsRefreshing, productsSubmitting, categoryAttributeWarmup) before trusting counts or reading the attribute list. A dropdown field takes options[].value, never its position in the list. Full walkthrough (every step type's payload, the product-filter flags, optionsPending, the deferred-attribute branch): call get_koongo_help with slug 'ad-wizard-steps'. ad_id is from list_ads / create_ad. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects).

  Connector

  Destructive

  OAuth

• workflows_list_node_typesA

  neonloopsA

  Lists the step types a neonloops workflow is built from: a Start that fires on demand, on a schedule, from a webhook or when an app event happens, AI agents, branches, loops, app actions and more. For each it gives the label, category, the JSON Schema of its config, the fields that schema requires, and notes on rules a schema cannot express. Read it before configuring a step type for the first time with workflows_edit; workflows_get shows how the steps already in a workflow are configured. A step refers to an earlier step's result only as nodes.<key>.output.<field>, and a reference that skips output or names a key no step has is refused by name, with the corrected path. It takes no arguments, and its large answer is the same for every workspace, so one read per session is enough.

  ConnectorAPI key

• submit_workflowA

  BotverseA

  Submit a multi-step workflow to the Botverse workflow engine. Steps execute in dependency order; parallel branches (multiple steps with the same depends_on) run simultaneously. Returns a workflow_id immediately — poll get_workflow_status every 5–10 seconds until terminal. INTER-STEP REFERENCES: pass a prior step's output into a later step with the string "$.steps.<step_id>.output_key" (e.g. a docx→pdf chain: step to_pdf has depends_on: ["to_docx"] and inputs {"source_url": "$.steps.to_docx.output_key", "output_format": "pdf"} using tool convert_from_url — no input_format needed here, it's inferred from the source file extension; input_format is only required by convert_content, which has no filename to infer from). Workflow params are referenced as "$.params.<name>". No other template syntax (${...} etc.) is supported. BILLING: convert-only workflows run on wallet balance ($0.05/step). Workflows containing transcode or transcribe steps require auto-refill to be enabled at botverse.cloud/dashboard/billing (their cost scales with source duration). Workflow definition uses BWDL (Botverse Workflow Definition Language) — schema at botverse.cloud/schemas/workflow/v1.json.

  ConnectorNo auth