Skip to main content
Glama

Native mistral ocr

native_mistral_ocr

Process a document through the organization's private Mistral connection. Requires an organization API key and recorded native consent. Sends the original document without the privacy barrier. A required organization privacy barrier blocks this tool before dispatch. Use an available native OCR model. Provider errors and charges retain their original meaning. Requires an organization API key, an active provider connection and a configured RN contract. Uses the organization's pool first. An inherited pool requires native consent from the consumer and supplier. The original provider body and model are preserved. Personal data is sent without the privacy barrier. An organization can set privacy_barrier_required in its inference settings. That requirement overrides key consent: native requests return 403 organization_privacy_barrier_required before body processing, billing or provider dispatch. The requirement also applies when the supplying organization's pool requires the barrier. Use /v1/chat/completions and the protected rota/* catalog when the request requires that barrier. Resources remain scoped to the organization and the connection that created them. A submitted request is not retried by the gateway. Provider charges remain on the connected provider account. Provider HTTP errors retain their status and original body; a provider 400 is not replaced with a gateway 502. Unsupported model parameters are not removed or translated. Omit X-RN-Connection-Id to select from the authorized pool. RN reserves its contracted fee before dispatch. Provider charges for an owned key remain on that provider account. Token tariffs and positive reference percentages require verified usage limits and provider counters. For OpenAI-compatible streaming under these tariffs, send stream_options.include_usage=true. Positive charges for opaque or batch creation calls require a per-request tariff when usage cannot be reconciled in that response. Unknown execution remains pending; the gateway does not invent zero usage or repeat the paid request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>",
      "document": "<document>"
    },
    "name": "native_mistral_ocr"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesNative Mistral OCR model identifier, such as mistral-ocr-4-1.
pagesNoOptional string page range, such as 0-5, or an array of zero-based integer page numbers.
documentYesOriginal Mistral document: file_id, document_url or image_url, with its native type.
table_formatNoNative Mistral table format.
extract_footerNoRequest native footer extraction.
extract_headerNoRequest native header extraction.
include_blocksNoRequest native page blocks and geometry.
include_image_base64NoReturn extracted image data when requested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses that the original document and personal data bypass the privacy barrier, explains pre-dispatch 403 blocking, and describes pool and consent behavior. It also covers provider error passthrough, unsupported-parameter handling, charges, fee reservation, lack of gateway retries, and pending unknown execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and privacy risk are front-loaded, but the long single block repeats API-key, privacy, provider-charge, and error information. Streaming tariffs, batch creation, and other generic billing rules dilute the OCR-specific guidance and make important behavior harder to locate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Together with the fully documented schema, the description supplies unusually complete prerequisites, routing, privacy, billing, error, and retry context for a complex operation. With no output schema, however, it should briefly characterize the successful OCR response instead of spending so much space on generic tariff scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all eight parameters, including the nested document forms and page selection. The description adds only limited model and native-passthrough context; details such as X-RN-Connection-Id and stream_options are outside this tool's input schema rather than explanations of its parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening identifies document processing through an organization's private Mistral connection, and later references to a native OCR model clarify the operation. It also distinguishes this native path from the protected chat-completions route, although it never directly states that the tool extracts text or document structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete prerequisites: an organization API key, native consent, an active provider connection, and a configured RN contract. It explicitly says the privacy-barrier requirement blocks this tool and directs requests needing that barrier to /v1/chat/completions and the protected rota/* catalog.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources