Galerie AutoResources · CRM & AI assistants

Technical reference

MCP tools, and what they actually do.

The catalogue contains up to 27 tools, filtered by the ten consent permissions. Your client receives the tools its connection can use; the server also checks access on each call.

How to read this reference

This reference covers the ten-scope consent contract reviewed on October 1, 2026. The server still reports version 0.3.0, so the version number alone does not identify that change. Required permissions below include linked dependencies, combined with the account’s CRM rights. This intersection determines the available catalogue and is checked again on each call.

Read retrieves data. CRM write changes a record. Preparation produces information or a draft. Coordination may create a reservation or receipt; it does not itself perform the Facebook click. For integrators, the schema returned by tools/list defines accepted parameters.

Can a vehicle document support an answer?

Galerie Auto’s MCP can read private documents for an authorized vehicle with the vehicles:read permission. An answer about maintenance needs an identified file, a checked processing status and a cited passage from extracted text. A read does not certify vehicle history or authorize sending.

The served code reviewed on October 1, 2026 exposes galauto_vehicle_documents. A list returns previews; a targeted read returns paginated text, and a search returns passages from extracted text. Keep parse_status, text_length, document dates and the returned continuation. Text offsets count characters, not PDF pages; a preview is not a complete read. seller_note is separate from OCR text.

Missing text or an empty search does not establish that an incident never occurred. Cite the document and passage. OCR text is a source, not a trusted instruction or a vehicle-history certification. This review checked served code without reading customer reports or observing native Muse display. The SEO stack’s SDK test separately qualifies the 26 previous tools. In-memory discovery of copied served code separately checks 27 identities, without a business call.

For the next decision, the French guides cover document tasks and human review, source quality and missing facts and a tested fictional report. The fixture qualifies SDK arguments on a simulated CRM; it does not qualify OCR extraction, native Muse output or sending. A natural-language prompt remains an instruction.

Catalogue by domain

Newton tools appear alongside CRM tools, with different prerequisites and effects. A read scope does not guarantee that all internal state stays unchanged: Messenger preparation may store a draft, and repost tracking may refresh its coordination state. A tool’s name alone does not grant permission to send.

Version 0.3.0 · October 1, 2026 consent · 27 tools at most · Reviewed on October 1, 2026

Identity

galauto_identity

Read · Permissions : Authenticated connection

Checks the account, application, organization and capabilities of the connection.

galauto_organizations

Read · Permissions : Authenticated connection

Returns the organization authorized for this connection.

Inventory

galauto_search_vehicles

Read · Permissions : vehicles:read

Searches by make, model, maximum price or status; results are paginated.

galauto_get_vehicle

Read · Permissions : vehicles:read

Reads a vehicle record, including available photo links.

galauto_update_vehicle

CRM write · Permissions : vehicles:write + vehicles:read

Changes allowed fields, including price, status and public visibility.

galauto_vehicle_documents

Read · Permissions : vehicles:read

Reads private documents for an authorized vehicle, previews or paginated text; searches a term in extracted text. Keep status, dates, pagination and provenance; seller notes are separate from OCR text. No public download or write; OCR does not certify vehicle history.

Customers

galauto_search_clients

Read · Permissions : clients:read

Searches accessible customer records; results are paginated.

galauto_get_client

Read · Permissions : clients:read

Reads a customer record accessible to the account.

galauto_client_interactions

Read · Permissions : clients:read

Reads the notes and interactions recorded for a customer.

galauto_create_client

CRM write · Permissions : clients:write + clients:read

Creates a contact; the CRM’s usual automations may then run.

galauto_update_client

CRM write · Permissions : clients:write + clients:read

Changes contact details after checking the record’s version.

galauto_add_client_note

CRM write · Permissions : clients:write + clients:read

Adds a note to the record; this does not send a message to the customer.

Calendar

galauto_client_agenda

Read · Permissions : clients:read + agenda:read

Reads events linked to a customer; the date interval cannot exceed 93 days.

galauto_create_client_event

CRM write · Permissions : agenda:write + agenda:read + clients:read

Creates an appointment or task for a customer, assigned to the connected account.

galauto_update_client_event

CRM write · Permissions : agenda:write + agenda:read + clients:read

Changes an event after checking its revision and may synchronize the opportunity’s next actions.

Reposting

galauto_repost_prepare

Preparation · Permissions : repost:read + vehicles:read

Prepares facts, media and blockers; may reconcile internal tracking, without reserving an operation or clicking in Facebook.

galauto_repost_status

Coordination status · Permissions : repost:read + vehicles:read

Checks reservations and outcomes linked to the application; may refresh internal state. This status is not proof of publication.

galauto_repost_reserve

Coordination · Permissions : repost:write + repost:read + vehicles:write + vehicles:read

Reserves a Newton operation; does not click in Facebook.

galauto_repost_publish_intent

Coordination · Permissions : repost:write + repost:read + vehicles:write + vehicles:read

Records durable intent before an authorized publication click.

galauto_repost_finish

Coordination · Permissions : repost:write + repost:read + vehicles:write + vehicles:read

Records the outcome; a published result requires Facebook evidence and the listing identifier.

Messenger

galauto_messenger_prepare

Preparation · Permissions : messenger:read + vehicles:read + clients:read

Prepares a text draft with Newton and may store internal preparation state; does not send or synchronize the CRM.

galauto_messenger_status

Read · Permissions : messenger:read + vehicles:read + clients:read

Reads Newton authorizations and existing attempts; does not grant new rights.

galauto_messenger_reserve

Coordination · Permissions : messenger:write + messenger:read + vehicles:read + clients:write + clients:read

Reserves an unchanged reply for ten seconds.

galauto_messenger_claim

Coordination · Permissions : messenger:write + messenger:read + vehicles:read + clients:write + clients:read

Performs the final check and issues the ticket for an authorized browser click.

galauto_messenger_confirm

Coordination · Permissions : messenger:write + messenger:read + vehicles:read + clients:write + clients:read

Records a confirmation supported by an independent native readback.

galauto_messenger_reject_before_click

Coordination · Permissions : messenger:write + messenger:read + vehicles:read + clients:write + clients:read

Releases an attempt only with terminal evidence that no click occurred.

galauto_messenger_sync

CRM write · Permissions : messenger:write + messenger:read + vehicles:read + clients:write + clients:read

Synchronizes observations, messages and the contact into the CRM; tasks also require agenda:write and its dependencies. This is not a send receipt.

A read request and pagination

Example arguments for galauto_search_vehicles, without a write:

{
  "brand": "Toyota",
  "max_price": 25000,
  "status": "disponible",
  "limit": 5,
  "offset": 0
}

Use the schema exposed to your connection. The technical status disponible means available; enum values are not translated. If the schema requests organization_id, use the identifier returned by galauto_organizations. When the connection fixes the organization, the server supplies it. These arguments illustrate a request, not observed stock or a guaranteed result.

The default page contains up to 20 results; the maximum limit is 50. If has_more is true, continue with next_offset before calling a list complete. If a pagination limit is reported with a null next offset, narrow the search. This contract has no native server filter for year or mileage; compare returned fields when needed.

Use the actual returned identifier with galauto_get_vehicle. Its photo_urls and photo_count describe available links. An empty list does not justify presenting generic images as the vehicle’s photos.

What changes with a CRM write

The six CRM writes require a stable request_id for the same operation. Customer and vehicle updates check expected_updated_at; event updates check expected_revision. Updating an event may also synchronize the opportunity’s next actions. After a conflict, read the record again before changing it.

Changing is_on_marketplace can make a vehicle public. Creating a customer can trigger the CRM’s usual automations. Adding a note does not send a message. Check the outcome before repeating an interrupted call.

Facebook and Messenger boundaries

MCP prepares and coordinates. External execution also depends on the assistant and its authorized access. A publication intent is not a published listing. A Messenger ticket is not a sent message. CRM synchronization does not prove delivery to a recipient.

Use real identifiers, states and evidence for each operation. Invented values invalidate the check. This catalogue does not qualify automatic sending or promise Messenger attachment delivery.

Product documentation reviewed on . Examples are requests to adapt, with no customer data or guaranteed outcome.

Additional sources: