"Task" matching MCP tools:

• task-analysisA

  MeshMarketA

  Task Analysis — Hand a task, get a structured plan back — typed steps, risks, and a go/caution/no-go verdict. Runs claude-haiku-4.5 — the response names the model that served the call. Input: {task: string}. Returns {analysis: {summary, steps, risks, verdict}, model}. (5 MESH/call, a tool · reasoning)

  ConnectorNo auth

• taskA

  TrueClicksA

  Get tasks as JSONL. Limited to tasks created in the last 365 days.

  ConnectorOAuth

• task-orchestrateC

  MeshMarketA

  Task Orchestrate — Break a multi-step task into an execution plan any agent can follow. Powered by api.meshtool.ai. Input: { task: string, tools: array }. (6 MESH/call, a tool · reasoning)

  ConnectorNo auth

• order-task-writeA

  WayfrontA

  Create, update, delete, complete or reopen order tasks. Every action requires order_number. update/delete require task_id; complete/reopen without task_id apply to every eligible task on the order. deadline is in HOURS. employee_ids replaces staff assignments; for_client instead assigns the task to the client and can email them. Omitted update fields stay unchanged. Moving sort_order below reached workflow tiers can reset assignments.

  Connector

  Destructive

  OAuth

• Get-Running-Task-StatusA

  YouCam for CreatorsC

  Retrieves the current status and results of a previously initiated AI processing task. Use this tool when you need to check on a task that was started earlier but hasn't completed yet, or when a user returns to inquire about a task they initiated previously. WHEN TO USE THIS TOOL: - When a user provides a task_id from a previous session and wants to check if their result is ready - When a user asks about a task they started earlier (e.g., 'Is my hairstyle ready?', 'Check my previous request') - When resuming a conversation where a task was left processing - When a task exceeded the initial polling timeout and the user wants to see if it has completed

  ConnectorNo auth

• Get-Running-Task-StatusA

  YouCam for Beauty & Personal CareC

  Retrieves the current status and results of a previously initiated AI processing task. Use this tool when you need to check on a task that was started earlier but hasn't completed yet, or when a user returns to inquire about a task they initiated previously. WHEN TO USE THIS TOOL: - When a user provides a task_id from a previous session and wants to check if their result is ready - When a user asks about a task they started earlier (e.g., 'Is my hairstyle ready?', 'Check my previous request') - When resuming a conversation where a task was left processing - When a task exceeded the initial polling timeout and the user wants to see if it has completed

  ConnectorNo auth

• Get-Running-Task-StatusA

  YouCam for Fashion & RetailB

  Retrieves the current status and results of a previously initiated AI processing task. Use this tool when you need to check on a task that was started earlier but hasn't completed yet, or when a user returns to inquire about a task they initiated previously. WHEN TO USE THIS TOOL: - When a user provides a task_id from a previous session and wants to check if their result is ready - When a user asks about a task they started earlier (e.g., 'Is my hairstyle ready?', 'Check my previous request') - When resuming a conversation where a task was left processing - When a task exceeded the initial polling timeout and the user wants to see if it has completed

  ConnectorNo auth

• order-task-readA

  WayfrontA

  List visible tasks for an order. Requires order_number; supports filtering, sorting and pagination.

  ConnectorOAuth

• x402-task-routerD

  minia2a-mcpD

  Task Router: Route a task to the right service.

  ConnectorNo auth

• delete_taskA

  PlateA

  Permanently delete a task. Comments and attachments are removed automatically. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).

  Connector

  Destructive

  OAuth

• close_taskA

  KeelenA

  Close a task that should not be built — a duplicate, or work already shipped. Use this when a task on the board is obsolete: the change already landed in another PR, a sibling task covers it, or the user changed direction. The task is marked `cancelled` and keeps ALL of its history (acceptance criteria, QA steps, iterations) — nothing is deleted. `reason` is REQUIRED and is recorded on the audit trail; say why in one line. Pass `superseded_by_pr_number` (or `superseded_by_task_id`) when the work was genuinely delivered somewhere else — that records verified provenance instead of a bare abandon. Closing does NOT claim the content is on the default branch, so any task that declared a dependency on this one keeps waiting; deliver or re-plan those separately. Refuses with 409 while the task is being worked on by a running iteration (stop the machine first, or wait for it to finish). A task in another workspace 404s. Business-level replay guard: closing an already-closed task changes no task state. The call is not idempotent end to end — an authenticated request also persists credential-use state. The response echoes `open_tasks`: how many tasks are still open on the project, counted after the close commits. Check it — if it did not drop, the ticket was already closed and this call changed nothing. It is the same count `project_status` returns, and neither counts a closed task as open. Prefer this over leaving a dead task on the board: unfinished tasks count against the project's planning capacity, so stale duplicates quietly stop new roadmap items from being expanded.

  Connector

  Destructive

  No auth

• tascan_post_messageA

  TaScanA

  Post a message on a task trail (protocol v0.2 trail_messages): kind question, answer, handoff or discussion. A message never completes a task, never satisfies a gate and never pages anyone. The actor is stamped from your credential (key:<id>, actor_type "key" — a credential, never a human), never from the body; the executor and the reviewer consume a key's answers only when the key holds agent:dispatch. On an ordinary task this is write tier. On a CYCLE task (one with coord) it needs agent:dispatch (agent:dispatch:code when the task, or the asker a question task stands for, is CODE:/SHELL:) because the text can become executor prompt or reviewer input. kind=answer on a dispatcher-addressed question task answers it through coord_answer_question and releases the blocked asker; a human-addressed question is answered only on the worker page (403 here). finding (reviewer runner) and decision (human completion) cannot be posted. Body ≤ 8000 chars; idempotency_key makes a replay return the same message.

  ConnectorNo auth

• approve_physical_task_completionA

  Molt2MeetA

  Approve a completed task — SIMPLE FLOW ONLY. Precondition: the task was dispatched with publishImmediately=true (default) AND auto-funded from your wallet, i.e. you did NOT call request_task_quote/fund_task/publish_task (escrow flow). If you went through the escrow flow (any of those three tools), call approve_task_review instead — calling this on an escrow task returns an error with the correct tool to use. Mechanism: marks the task Completed and triggers the operator payout immediately. There is no review window for the simple flow. Task must be in ProofUploaded or UnderReview status. Requires: API key from register_agent. Next: monitor task.settled and task.closed via get_task_events — settlement happens automatically.

  ConnectorNo auth

• delete_use_caseA

  InterbangA

  Delete a use case from a draft UT, including every task inside it. Irreversible — check the useCaseId and its task list (from get_ut) before calling; prefer delete_task when you only mean to remove a single task. Only works on PREPARING drafts.

  Connector

  Destructive

  OAuth

• cancel_taskA

  AgentMarketplaceA

  Cancel a task you posted. Only legal before bidding/assignment closes it out. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task to cancel. Returns: The cancelled task on success. ``{"error_code": "not_found", ...}`` if the task doesn't exist, ``{"error_code": "authorization_failed", ...}`` if you're not the poster, or ``{"error_code": "invalid_input", ...}`` if the task is already past the cancellable stage.

  ConnectorNo auth

• submit_bidA

  AgentMarketplaceA

  Bid on an open task. Args: access_token: AgentAuth bearer token (requires ``market.bid``). task_id: UUID of the task to bid on. proposed_cost_units: Your price, as an **integer** amount_units. Never a float or Decimal — money is integer units end to end. estimated_duration_seconds: How long you expect the work to take. proposed_approach: Free-text summary of how you'll do the work. terms: Optional JSONB — anything else worth stating up front. confidence_score: Your self-assessed confidence, 0.0-1.0. Returns: The created bid (status ``"pending"``). The task moves to ``"bidding"`` on its first bid. Errors: ``not_found`` (no such task), ``invalid_input`` (bidding on your own task, past bid_deadline, an existing pending bid, or a task not open for bidding).

  ConnectorNo auth

• review_resultA

  AgentMarketplaceA

  Review the assignee's latest submitted result. One tool, three actions — not three tools (PLAN.md §5). - ``accept``: task -> completed. Response includes a ``report_interaction_hint`` — file your own AgentTrust report_interaction for mutual confirmation (PLAN.md §7.4); the marketplace already files its own first-party report. - ``reject``: task -> failed (terminal — not a revision request). Response includes both a ``report_interaction_hint`` (outcome ``"failure"``) and a ``file_dispute_hint``. - ``request_revision``: task -> in_progress. The assignee resubmits via ``submit_result``. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task under review. action: One of ``accept``, ``reject``, ``request_revision``. reviewer_notes: Optional free-text feedback, recorded on the result. Returns: ``{"task": ..., "result": ...}`` plus hints on accept/reject. Errors: ``not_found`` (no task, or no submitted result to review), ``authorization_failed`` (not the task's poster), ``invalid_input`` (unknown action or task not in ``review``), ``rate_limit_exceeded``.

  ConnectorNo auth

• approve_task_reviewA

  Molt2MeetA

  ESCROW FLOW ONLY. For direct-settlement tasks (settlementMode='direct') use acknowledge_direct_settlement_task instead — this endpoint returns 400 with a pointer when called on a direct task. Approve a completed task after reviewing the proof. Triggers payout to the operator. The task must be in UnderReview status AND settlementMode='escrow'. Funds move from locked to earned. Requires authentication.

  ConnectorNo auth

• cancel_scheduled_taskA

  Valuein — SEC EDGAR Fundamentals & Smart-Money DataA

  Cancel a pending scheduled task by id (from schedule_task or list_scheduled_tasks). Only a `pending` task can be cancelled — one that already woke (completed) cannot be un-woken. Idempotent: cancelling an already-cancelled task is a no-op. Tier: sp500+ (sample rejected).

  Connector

  Destructive

  No auth

• task_addA

  kanban-todo-tasks-projects-boardA

  Add one task to a board and return its id, board and column. The board is created on first use, so pass an existing project or leave it out. An identical open task is refused. Free: 3 boards, 200 open.

  ConnectorNo auth

• task_addA

  standupA

  Add one task to a board and return its id, board and column. The board is created on first use, so pass an existing project or leave it out. An identical open task is refused. Free: 3 boards, 200 open.

  ConnectorNo auth