> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lexera.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Tools Overview: Invocation, Auth, and Payloads

> Understand how Lexera's MCP tools are invoked over SSE with JSON-RPC 2.0, which tools require Bearer authentication, and what each tool returns.

The Lexera Protocol exposes its capabilities as **Model Context Protocol (MCP) tools** invoked with JSON-RPC 2.0 messages over a Server-Sent Events connection. This page summarizes every tool, its authentication requirement, and how to invoke it.

## Invocation pattern

Every MCP tool is called through the same JSON-RPC method: `tools/call`. The `params.name` field selects which tool to run, and `params.arguments` carries the tool-specific payload.

```json JSON-RPC skeleton theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "<tool_name>",
    "arguments": { }
  }
}
```

Send this payload as a POST to the session URL you receive from the SSE stream. The POST returns `HTTP 202 Accepted`, and the tool's execution result is streamed back over the open SSE connection.

<Info>
  For the full transport walkthrough, see [Execution Lifecycle](/concepts/execution-lifecycle).
</Info>

## Available tools

<CardGroup cols={2}>
  <Card title="lexera_local_statutory_audit" icon="scale-balanced" href="/tools/lexera-local-statutory-audit">
    Free, unauthenticated statutory compliance check. Part of the anonymous PLG funnel.
  </Card>

  <Card title="lexera_check_jurisdiction_rates" icon="tag" href="/tools/lexera-check-jurisdiction-rates">
    Query the AED wallet hold required for a given jurisdiction before dispatch.
  </Card>

  <Card title="lexera_route_to_specialist" icon="paper-plane" href="/tools/lexera-route-to-specialist">
    Dispatch a document to a human attorney queue. Places a temporary AED wallet hold.
  </Card>

  <Card title="lexera_get_order_status" icon="magnifying-glass" href="/tools/lexera-get-order-status">
    Poll a dispatched order for status and, once complete, certified artifact URLs.
  </Card>
</CardGroup>

## Authentication requirements

| Tool                              | Authentication            | Wallet hold                                 |
| --------------------------------- | ------------------------- | ------------------------------------------- |
| `lexera_local_statutory_audit`    | Not required (PLG funnel) | None                                        |
| `lexera_check_jurisdiction_rates` | Bearer token              | None (read-only pricing)                    |
| `lexera_route_to_specialist`      | Bearer token              | Temporary AED hold at the jurisdiction tier |
| `lexera_get_order_status`         | Bearer token              | None                                        |

<Note>
  Even for unauthenticated tools, the same SSE + JSON-RPC transport applies. See [Authentication](/authentication) for header formatting.
</Note>

## Typical flow

<Steps>
  <Step title="Preflight pricing">
    Call `lexera_check_jurisdiction_rates` to see the required AED hold for the target jurisdiction.
  </Step>

  <Step title="Dispatch the document">
    Call `lexera_route_to_specialist` with the document text, jurisdiction, and specialist instructions. Capture the returned `order_id`.
  </Step>

  <Step title="Poll for completion">
    Call `lexera_get_order_status` with the `order_id` until `current_status` becomes `verified_executed`.
  </Step>

  <Step title="Download the artifact">
    Fetch `certified_redline_url` with your Bearer token to receive the law firm-certified `.docx`.
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Wallet and pricing" icon="wallet" href="/concepts/wallet-and-pricing">
    How AED holds and jurisdiction tiers work.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/reference/errors">
    HTTP codes and streamed JSON error payloads.
  </Card>
</CardGroup>