Tool reference · Workspace

get_approval

The status of a proposal made with any propose_* tool: pending, approved, sent, rejected, failed or expired

read-onlyreads the workspacenot rate limited

Updated 2026-09-18 · Server 2.0.0

What it does

Close the loop on a proposal: did a person approve it, and did it go out?

Arguments

NameTypeRequiredMeaning
idstringyesThe approval id returned by a propose_* call

This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:

inputSchema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The approval id returned by a propose_* call"
    }
  },
  "required": [
    "id"
  ]
}

Request

Paste this, swap the key, and you have called the tool.

curl
curl -s https://topclozer.com/api/mcp \
  -H "Authorization: Bearer tcz_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_approval",
      "arguments": { "id": "apr_mf3k2a9x1" }
    }
  }'

Returns

{ id, kind, status, target, text, created_at, decided_at, sent_at, error }. status: pending → approved → sent, or rejected / failed / expired.

The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.

payload
{ "id": "apr_mf3k2a9x1", "kind": "connection_request", "status": "sent", "target": { "name": "Dana Whitfield", "providerId": "ACoAAB1x…" }, "text": "Hi Dana — …", "created_at": "2026-10-02T09:14:03Z", "decided_at": "2026-10-02T09:40:11Z", "sent_at": "2026-10-02T09:46:52Z", "error": null }

Worth knowing

Reads the workspace database only. error carries the reason when an approved send is waiting (a limit, a slow-down) or failed.

Limits

No request limit. This tool reads the workspace database and costs nothing to serve. The limits that bite in this product are the sending controls — per-sender weekly invite caps, the warm-up ramp, the working-hours window and a randomised gap between actions — and no tool can raise them.

Related tools

All 65 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.