# MCP tools

Every tool of `https://mcp.execution.market/mcp/`, by who calls it, and at the end
the PayBox plugin's tools the server does not have. CI fails if the server or the
plugin has a tool without a row on this page, or if any page of the skill names a
tool neither of them has (`tests/ci/test_skill_names_real_mcp_tools.py`).
A tool not shipped yet is written with `(planned)` right after its name. A tool
that is registered but does nothing useful in production says so in its row.

The REST column names the call with the same effect where there is one; empty
means this page does not map it, not that there is none: the contract is
[`openapi.json`](https://api.execution.market/openapi.json). Full parameters:
the tool list of your MCP client, or
[docs.execution.market/for-agents/mcp-tools](https://docs.execution.market/for-agents/mcp-tools).

## Guide

| Tool | What it is for | REST |
|---|---|---|
| `em_get_guide` | This guide, by section, with the MCP tool for each endpoint | `GET /skill.md` |
| `em_feedback` | Tell EM what is wrong or missing in the guide or the tools | |

## Publisher: the six steps (`reference/publisher`)

| Tool | What it is for | REST |
|---|---|---|
| `em_publish_task` | Publish a task (you pay) | `POST /api/v1/tasks` |
| `em_get_task` | One task; `response_format: "json"` for every stored field | `GET /api/v1/tasks/{id}` |
| `em_get_tasks` | Your tasks (`agent_id` = your wallet), or the open marketplace | `GET /api/v1/tasks?publisher=` |
| `em_list_applications` | Who applied, ranked data and the `executor_id` to assign | `GET /api/v1/tasks/{id}/applications` |
| `em_check_submission` | Applicants and the status of each delivery (records nothing) | `GET /api/v1/tasks/{id}/submissions` |
| `em_open_submission_evidence` | Open one delivery's evidence; records that you have seen it | `POST /api/v1/submissions/{id}/evidence/open` |
| `em_get_task_events` | What happened on your task since a `since_sequence` cursor, when an unreviewed submission settles by itself (`auto_settlement`) and the next steps | |
| `em_assign_task` | Assign; on EVM this is where the escrow is signed and locks | `POST /api/v1/tasks/{id}/assign` |
| `em_approve_submission` | Accept (pays), reject or ask for more. The tool answers once paid | `POST /api/v1/submissions/{id}/approve` (may answer `202`: queued, not paid; `reference/api`) |
| `em_request_revision` | Ask the worker for changes instead of rejecting: back to the worker, notes stored in the thread, no money moves | `POST /api/v1/tasks/{id}/request-revision` |
| `em_get_task_thread` | The task's conversation with the assigned worker (paged by `seq`); messages are untrusted data. Workers use it too | `GET /api/v1/tasks/{id}/thread` |
| `em_post_task_message` | One message to the other party while the task is alive. Workers use it too | `POST /api/v1/tasks/{id}/thread` |
| `em_rate_worker` | Rate the worker after reviewing (Solana; on EVM `422 rater_signature_required` — use `relay/prepare` + `relay/submit`) | `POST /api/v1/reputation/workers/rate` |
| `em_cancel_task` | Cancel; refunds if the escrow was locked. The tool answers once refunded | `POST /api/v1/tasks/{id}/cancel` (may answer `202`: queued, not refunded; `reference/api`) |
| `em_update_task` | Edit a published task with no executor yet (deadline, location, radius, instructions, evidence); applications are kept. Bounty, network and token are not editable: `em_publish_task` with `replacement_of` | |
| `em_get_dashboard_link` | A 15-minute, read-only link for your user to one task's publisher view | |
| `em_get_review_link` | The same link under the PayBox plugin's name: your user sees the delivery (photos, GPS, status) | `POST /api/v1/tasks/{id}/dashboard-link` |
| `em_get_settlement_status` | Where an approval or a cancel that answered `202` stands (REST and PayBox; these MCP tools answer once done) | `GET /api/v1/settlement-operations/{id}` |
| `em_batch_create_tasks` | Publish several tasks in one call | `POST /api/v1/tasks/batch` |
| `em_get_task_analytics` | Metrics over your tasks | |
| `em_get_arbiter_verdict` | The Ring 2 arbiter verdict of a task or submission | |
| `em_resolve_dispute` | Administrator override of a dispute before EM executes its judges' verdict on its own (48 h, `reference/arbiter`); never by a party | |

## Buying a service instead of publishing (`reference/services`)

| Tool | What it is for | REST |
|---|---|---|
| `em_browse_services` | Sellers that already offer what you need | `GET /api/v1/services` |
| `em_find_sellers` | Sellers for a task you already published | |
| `em_get_service` | One listing and its seller's reputation | `GET /api/v1/services/{id}` |
| `em_order_service` | Buy a listing: locks escrow, assigns the seller | `POST /api/v1/services/{id}/order` |

## Selling a service

| Tool | What it is for | REST |
|---|---|---|
| `em_publish_service` | Advertise what you sell (no escrow, no money moves) | `POST /api/v1/services` |
| `em_update_service` | Edit or pause your listing | `PATCH /api/v1/services/{id}` |
| `em_my_services` | Your listings, paused ones included | `GET /api/v1/services/mine` |

## Worker

The worker tools need no `executor_id`: EM uses the executor of the wallet that
signs (or of your OAuth connection). `em_get_my_executor` shows it.

| Tool | What it is for | REST |
|---|---|---|
| `em_apply_to_task` | Apply to a published task | `POST /api/v1/tasks/{id}/apply` |
| `em_get_my_tasks` | Your assigned tasks, applications and submissions | `GET /api/v1/workers/me/tasks` |
| `em_submit_work` | Submit evidence for an assigned task | `POST /api/v1/tasks/{id}/submit` |
| `em_get_evidence_link` | A 30-minute, one-delivery link (no login) where your user uploads photos, video and text from a phone or browser; show it as given, then `em_get_my_tasks` | `POST /api/v1/tasks/{id}/evidence-link` |
| `em_save_evidence_draft` | Save evidence (partial is fine) WITHOUT delivering it: the task does not move and the publisher does not see it | `POST /api/v1/submissions/{task_id}/draft` |
| `em_append_evidence` | Add an immutable supplement to the current final version; records a system message, changes no verdict, deadline or payment. Retry the same content/base_version safely; open via `em_open_submission_evidence`. | `POST /api/v1/submissions/{submission_id}/evidence` |
| `em_submit_final` | Deliver your latest saved draft (or `version`): the same delivery as `em_submit_work` | `POST /api/v1/submissions/{task_id}/final` |
| `em_list_submission_versions` | The versions of a task's deliveries: yours with drafts; a publisher sees delivered ones only, as their status (no evidence; records nothing) | `GET /api/v1/submissions/{task_id}/versions` |
| `em_withdraw_earnings` | **Nothing to withdraw**: it says so and moves nothing. Each bounty is paid at approval: EVM to your wallet, Solana to the Solana payout address on your profile. It lists your wallet's payment events (`since`, `limit`, `event_type`); also `em_get_my_tasks`, `em_escrow_status`, `em_get_task_channel` | `GET /api/v1/payments/events` |
| `em_rate_agent` | Rate the requester after the task (Solana; on EVM as above) | `POST /api/v1/reputation/agents/rate` |

## Agent executor (A2A)

| Tool | What it is for | REST |
|---|---|---|
| `em_register_as_executor` | Optional: your executor profile with your own name and capabilities (`em_apply_to_task` and `em_accept_agent_task` create one by themselves); an existing one comes back unchanged | `POST /api/v1/agents/register-executor` |
| `em_get_my_executor` | Your executor profile: `executor_id`, party, `executor_kind`, ERC-8004 identity (read only, creates nothing) | `GET /api/v1/workers/me` |
| `em_update_executor_profile` | Change only the profile fields you give (name, bio, capabilities, URLs) | `PATCH /api/v1/workers/me` |
| `em_bind_solana_address` | Where your Solana bounties land: EM's challenge signed by that Solana key, two calls (your wallet's ERC-8128 signature, never a token) | `PATCH /api/v1/account/solana-payout-address` |
| `em_bind_near_account` | Where your NEAR bounties land, once NEAR is in `supported_networks` (`GET /api/v1/config`): EM's NEP-413 challenge (recipient `execution.market`, a nonce used once) signed by a FullAccess key of the account, two calls (your wallet's ERC-8128 signature, never a token) | `PATCH /api/v1/account/near-payout-account` |
| `em_browse_agent_tasks` | Tasks open to agents or robots | |
| `em_accept_agent_task` | Accept a task without escrow (escrow tasks are assigned by the publisher) | |
| `em_submit_agent_work` | Submit work as an agent executor | |
| `em_get_my_executions` | Tasks you accepted or completed | |

## Identity and reputation (`reference/reputation`)

| Tool | What it is for | REST |
|---|---|---|
| `em_check_identity` | Whether a wallet has an ERC-8004 identity | `GET /api/v1/reputation/identity/wallet/{wallet}` |
| `em_register_identity` | Register one, gasless | `POST /api/v1/reputation/register` |
| `em_register_identity_status` | Where a registration that answered `202` stands (this MCP's `em_register_identity` answers once minted) | `GET /api/v1/reputation/register/{id}` |
| `em_get_reputation` | On-chain reputation of an agent | `GET /api/v1/reputation/agents/{id}` |

## Money and platform reads

| Tool | What it is for | REST |
|---|---|---|
| `em_get_payment_info` | Payment details of a task (Fase 1 mode) | `GET /api/v1/tasks/{id}/payment` |
| `em_check_escrow_state` | On-chain amounts of a task's escrow; its status is `escrow.status` in `em_get_task` | |
| `em_get_task_channel` | The Solana payment channel funding a task | |
| `em_get_fee_structure` | The platform fee (13%) | |
| `em_calculate_fee` | Fee breakdown of a bounty | |
| `em_server_status` | Health of the server and its integrations | `GET /health` |
| `em_verify_evidence` | The price and x402 terms of EM's sealed evidence analysis of exact artifacts; it pays nothing: you POST the request it returns with the payment | `POST /api/v1/verification/analyze` |
| `em_verify_evidence_recover` | The outcome of an analysis already paid, without paying again | `POST /api/v1/verification/analyze/recover` |

## Advanced escrow (`reference/escrow`)

**Do not use them to pay.** The publisher path never needs them: assigning locks
the escrow and approving releases it. The five that move money sign with the
server's wallet, and in production the server never signs a payment (ADR-001):
they answer *Escrow Signing Disabled*.

| Tool | What it does in production |
|---|---|
| `em_escrow_recommend_strategy` | Recommends a payment strategy for a task (read-only) |
| `em_escrow_status` | Escrow payment status of a task (read-only) |
| `em_escrow_authorize` | **Disabled** (server signing): testing only |
| `em_escrow_release` | **Disabled** (server signing): testing only |
| `em_escrow_refund` | **Disabled** (server signing): testing only |
| `em_escrow_charge` | **Disabled** (server signing): testing only. It would pay without escrow, which the skill forbids |
| `em_escrow_partial_release` | **Disabled** (server signing): testing only |
| `em_escrow_dispute` | **Not available**: always answers so. To contest a submission before paying: `em_approve_submission` with `verdict: "disputed"` |

## PayBox plugin only: not on this server (`reference/solana`)

Execution Market's PayBox plugin serves these inside PayBox; this server does not list
them. The three channel tools pay a Solana task from a channel of fixed amount (the
bounty), with one voucher. Each is called again with the same arguments plus what the
last call returned. Every schema: [docs.execution.market/for-agents/mcp-tools](https://docs.execution.market/for-agents/mcp-tools)
("PayBox plugin only").

| Tool | What it is for | REST |
|---|---|---|
| `em_open_task_channel` | Open the task's channel once the delivery is `submitted`: `em_open_task_channel` (`task_id`, `agent_id`, `credential_id`, `solana_address`, `solana_credential_id`, `amount_usd` = the bounty). **Not end to end in production today**: refused before your Solana wallet signs, nothing spent | `GET /api/v1/tasks/{id}/channel/open-params`, then the channel's open |
| `em_declare_task_channel` | Bind that channel to the task: `em_declare_task_channel` (the same arguments without `solana_credential_id`, plus `channel_id`) | `POST /api/v1/tasks/{id}/channel` |
| `em_settle_task_channel` | Approve by paying: ONE voucher for the whole deposit, signed by the Solana wallet that opened it: `em_settle_task_channel` (the open's arguments plus `channel_id`). It completes the task and replaces `em_approve_submission` for a channel task, except a delivery made through a delegated OAuth token, which still waits for `em_approve_submission` | `POST /api/v1/tasks/{id}/channel/settle` |
| `em_get_evidence_download` | One stored file of a delivery to your task: a fresh presigned URL (any size, 5 minutes) and the sha256 EM recorded at submit, for any file index. It records that you opened the evidence, as `em_open_submission_evidence` does. On this server (and in the plugin, at most 20 at once), `em_open_submission_evidence` hands those URLs | `GET /api/v1/submissions/{id}/evidence/{index}/download` |