---
title: "Rest Tool Dispatch"
method: POST
path: "/v1/tools/{tool_name}"
tags: ["mcp"]
---

# Rest Tool Dispatch

`POST /v1/tools/{tool_name}`

## Request

- Base URL: `https://api.slideforge.dev`
- URL: `https://api.slideforge.dev/v1/tools/{tool_name}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

REST alias over the MCP tool dispatch — same tools, same handlers, API-key auth.

Exists so the local stdio MCP wrapper (smartdatabrokers/slideforge-mcp) forwards as a
plain REST client, not an MCP proxy: the wrapper bakes the tool schemas in locally and
POSTs each call's `arguments` object here. Body shape == the MCP tool's inputSchema.
Returns the tool-result envelope (MCP content blocks). Cost events + wallet accounting
flow exactly as the /mcp/ tools/call path — this reuses the same dispatch.

## Path parameters

- `tool_name` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/slideforge/apis/slideforge-api.md) · [All operations](https://skmtc.dev/slideforge/apis/slideforge-api/llms.txt) · [OpenAPI document](https://skmtc.dev/slideforge/apis/slideforge-api/revisions/ae698e3d3c00?raw)