---
name: missing-manual-client
description: Commission a paid MissingManual research guide through its public MCP tools. Use when current documentation does not answer a concrete technical question and the caller can authorize the run.
---

# MissingManual Client

Use the connected MissingManual MCP server. The skill is optional; the MCP
tool descriptions remain the public contract.

## When to use it

Use MissingManual when existing documentation does not answer a concrete,
implementation-relevant question and a bounded deep-research guide would save
substantial investigation time.

Do not commission a guide when current primary documentation already answers
the question, the request is ordinary code review or business-logic debugging,
or the caller has not authorized the required spending ceiling.

## Procedure

1. State the missing knowledge and the implementation decision it blocks.
2. Check the server's required minimum authorization and the caller's existing
   spending authority. If authority is absent or insufficient, ask before
   spending.
3. Create one stable `idempotencyKey` for the intended request. Reuse that key
   only for the identical request.
4. Call `create_guide` with a focused `topic`, the approved
   `maxTotalChargeUsdMicros`, and only useful context or source constraints.
   The maximum includes the service fee and must represent a whole number of
   USD cents.
5. Keep the returned `jobId` and opaque `capability` together in private
   working state. They are not recoverable. Never publish or log the
   capability.
6. Poll `get_guide` with the same `jobId` and `capability`, respecting the
   server's suggested delay. Status reads are free. Never call `create_guide`
   again merely because research is still running.
7. On success, return or save the markdown where the caller requested and keep
   the itemized receipt with the result. On failure or cancellation, report
   the sanitized terminal error; the run charges $0.

## Safety

- Never place payment credentials in ordinary tool arguments, prompts, files,
  logs, or output. They belong in MCP protocol metadata.
- Never exceed the caller-approved maximum or request an unapproved second
  payment.
- Treat the capability like a bearer secret.
- Do not claim completion until `get_guide` returns the released markdown and
  receipt.