com.precision-concretecoating/mcp

Est-ce que com.precision-concretecoating/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.precision-concretecoating/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 33 outils

• analyze_estimate_photos≈ 260 tokens

  Runs visual observation over any unreviewed photos. Returns non-diagnostic observations from a fixed vocabulary with confidence values. Observations are impressions only and are always marked as requiring field verification.

  Paramètres, retour & exemple (3)

  Paramètres

  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.

  Exemple d'appel

  {"name": "analyze_estimate_photos", "arguments": {"request_id": "texte", "customer_access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• attach_estimate_photos≈ 1101 tokens

  Attaches photo references (public https URLs) to an estimate request. Photos support the estimator's preparation; they never replace the on-site inspection.

  Paramètres, retour & exemple (5)

  Paramètres

  • fields · object · optionnel
    Legacy internal-schema field bag. Prefer the top-level public fields; unknown keys are rejected. Never include pricing.
  • photos · array · requis
    Photo references to attach.
  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.

  Exemple d'appel

  {"name": "attach_estimate_photos", "arguments": {"photos": [], "request_id": "texte", "customer_access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cancel_estimate_appointment≈ 313 tokens

  Cancels a proposed or confirmed walkthrough, releases the held time back to Precision and notifies the office. The estimate request itself stays open, so a new appointment can be requested later.

  Paramètres, retour & exemple (5)

  Paramètres

  • reason · string · optionnel
    Why the customer is cancelling.
  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.
  • customer_authorized_cancellation · boolean · requis
    Must be true. The customer asked to cancel.

  Exemple d'appel

  {"name": "cancel_estimate_appointment", "arguments": {"request_id": "texte", "customer_access_token": "texte", "customer_authorized_cancellation": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• confirm_estimate_appointment≈ 338 tokens

  Confirms the appointment Precision proposed, using the proposal_id from the proposal. Only an unexpired proposal on this request can be confirmed. On success the walkthrough is booked, the office is notified and preparation instructions are returned.

  Paramètres, retour & exemple (5)

  Paramètres

  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • proposal_id · string · requis
    The proposal_id returned with the proposed appointment.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.
  • customer_confirmation · boolean · requis
    Must be true. The customer accepted the proposed time.

  Exemple d'appel

  {"name": "confirm_estimate_appointment", "arguments": {"request_id": "texte", "proposal_id": "texte", "customer_access_token": "texte", "customer_confirmation": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• create_estimate_request≈ 1151 tokens

  Creates a governed estimate request and returns a request_id plus a one-time customer_access_token. Required to create: customer_name, phone, project_city, project_state, project_type, consent_to_contact. Additionally required before submit_estimate_for_review: approximate_square_feet — these may be collected turn by turn with update_estimate_request. Every other field is genuinely optional.

  Paramètres, retour & exemple (24)

  Paramètres

  • email · string · optionnel
    Email
  • phone · string · requis
    Phone
  • source · string · optionnel · ai_assistant | website | developer_api
    Source
  • timezone · string · optionnel
    Timezone (IANA)
  • test_mode · boolean · optionnel
    Diagnostics only. Marks the request as a synthetic smoke-test record: it is excluded from reporting, never holds real calendar availability and never notifies the office. Never set this for a real customer.
  • postal_code · string · optionnel
    ZIP code
  • test_run_id · string · optionnel
    Diagnostics only. Correlates a synthetic test record with one automated smoke-test run. Ignored unless test_mode is true.
  • project_city · string · requis
    Project city
  • project_type · string · requis · garage | patio | commercial | driveway | pool_deck | warehouse | showroom | other
    Project type
  • customer_name · string · requis
    Customer name
  • project_state · string · requis
    Project state
  • customer_notes · string · optionnel
    Customer notes
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • project_address · string · optionnel
    Project street address
  • existing_surface · string · optionnel · bare_concrete | paint | epoxy | tile | adhesive | unknown
    Existing surface
  • project_timeline · string · optionnel
    Project timeline
  • requested_system · string · optionnel · full_flake | metallic | solid_color | commercial_system | urethane_cement | unsure
    Requested coating system
  • surface_condition · string · optionnel
    Surface condition
  • consent_to_contact · boolean · requis
    Consent to be contacted
  • customer_statement · string · optionnel
    The customer's own words for this step, stored verbatim as the evidence trail.
  • external_reference_id · string · optionnel
    External reference id
  • scheduling_preferences · object · optionnel
    What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly.
  • approximate_square_feet · integer · optionnel
    Approximate square feet
  • preferred_contact_method · string · optionnel · phone | text | email
    Preferred contact method

  Exemple d'appel

  {"name": "create_estimate_request", "arguments": {"phone": "texte", "project_city": "texte", "project_type": "garage", "customer_name": "texte", "project_state": "texte", "consent_to_contact": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• describe_platform≈ 206 tokens

  Self-documenting endpoint. Returns everything an AI agent or developer needs to use Precision OS correctly: platform identity and versions, authentication and read-only status, transports and capabilities, the complete auto-generated documentation for every registered tool, plus best practices, limitations, security model, privacy guarantees and data freshness. Generated dynamically from the live tool registry, so it never goes out of date.

  Paramètres, retour & exemple (1)

  Paramètres

  • tool · string · optionnel
    Return the documentation for a single registered tool instead of the whole catalog.

  Exemple d'appel

  {"name": "describe_platform", "arguments": {"tool": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain_knowledge_reasoning≈ 321 tokens

  Answers a question by traversing the published knowledge graph and returning ranked reasoning paths instead of disconnected records. Each path is an ordered chain of relationships with a path score, a path confidence, the supporting evidence, the relationship types used and a plain-language explanation of every transition. Traversal respects relationship weight, evidence strength, concept ontology, semantic clusters and inverse relationships, and prunes weak branches automatically.

  Paramètres, retour & exemple (5)

  Paramètres

  • goal · string · optionnel
    Optional destination topic. Paths that reach it rank higher.
  • subject · string · optionnel
    Optional explicit starting record title.
  • question · string · optionnel
    The question to reason about. Used to choose starting records and rank paths.
  • max_depth · integer · optionnel
    Maximum hops per reasoning path, 1–6. Default 4.
  • max_paths · integer · optionnel
    Maximum ranked paths returned, 1–12. Default 5.

  Exemple d'appel

  {"name": "explain_knowledge_reasoning", "arguments": {"goal": "texte", "subject": "texte", "question": "texte", "max_depth": 1, "max_paths": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_business_operations≈ 159 tokens

  Returns the approved public Business Operations & Project Lifecycle knowledge: how projects are quoted, scheduled, communicated, installed, completed, documented and supported. Company process knowledge, not coating science.

  Paramètres, retour & exemple (1)

  Paramètres

  • section · string · optionnel
    Restrict the response to a single lifecycle section, for example scheduling_process.

  Exemple d'appel

  {"name": "get_business_operations", "arguments": {"section": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_business_status≈ 109 tokens

  Returns the current scheduling availability of the business plus the standard project turnaround statements. Reflects the Current Availability control in Approved Knowledge.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_business_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_company_information≈ 110 tokens

  Returns the approved public profile of Precision Concrete Coating: organization identity, owner, services and verified context records. Sourced from the Approved Knowledge database.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_company_information", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_entity_relationships≈ 190 tokens

  Returns the approved relationship edges of the public entity graph, optionally filtered to one entity or one relationship type. Every edge references stable canonical entity ids on both sides; edges that touch an unpublished record are never returned.

  Paramètres, retour & exemple (2)

  Paramètres

  • entity · string · optionnel
    Canonical public id, slug or alias to centre the graph on.
  • relationship · string · optionnel
    Restrict the result to one relationship type.

  Exemple d'appel

  {"name": "get_entity_relationships", "arguments": {"entity": "texte", "relationship": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_estimate_intake_requirements≈ 139 tokens

  Read-only discovery. Returns every field the public estimate workflow accepts, which are required, the allowed enum values, the workflow states, the scheduling model and the guardrails. Call this first so no field name, enum value or state is ever guessed.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_estimate_intake_requirements", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_estimate_request_status≈ 252 tokens

  Returns the public projection of one estimate request: the workflow state, a customer-friendly status, what information is still missing, the recommended next question and the appointment (date, time window, timezone and confirmation status) if one exists. No internal notes, staff data or calendar availability is ever included.

  Paramètres, retour & exemple (2)

  Paramètres

  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.

  Exemple d'appel

  {"name": "get_estimate_request_status", "arguments": {"request_id": "texte", "customer_access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_faq≈ 102 tokens

  Returns every approved public question-and-answer pair collected from Approved Knowledge, the Warranty Center, Installation Standards and Inspection Standards.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_faq", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_knowledge_relationships≈ 198 tokens

  Returns the directional relationships between published Precision knowledge records — for example which installation standard mitigates which coating failure, or which warranty covers which service. Only relationships whose records are both approved and public are returned.

  Paramètres, retour & exemple (2)

  Paramètres

  • subject · string · optionnel
    Filter to relationships whose subject or object matches this text.
  • relationship · string · optionnel
    Filter to a single relationship type, e.g. mitigates, governed_by, verifies.

  Exemple d'appel

  {"name": "get_knowledge_relationships", "arguments": {"subject": "texte", "relationship": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_maintenance_care≈ 159 tokens

  Returns the approved public Maintenance & Care Center knowledge: how coated concrete should be cleaned, maintained, protected and inspected, including recommended methods, frequencies, prohibited products, common mistakes and warranty impact.

  Paramètres, retour & exemple (1)

  Paramètres

  • section · string · optionnel
    Restrict the response to a single care section, for example routine_cleaning.

  Exemple d'appel

  {"name": "get_maintenance_care", "arguments": {"section": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_next_estimate_question≈ 217 tokens

  Returns the single highest-value question still unanswered, in natural language, along with why it matters. Ask one question at a time and send the answer back through update_estimate_request.

  Paramètres, retour & exemple (2)

  Paramètres

  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.

  Exemple d'appel

  {"name": "get_next_estimate_question", "arguments": {"request_id": "texte", "customer_access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_pricing≈ 107 tokens

  Returns approved public pricing statements and the services they apply to. No quoted amounts are generated: Precision Concrete Coating prices every project after an on-site inspection.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_pricing", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_public_entities≈ 370 tokens

  Returns the approved Public Entity Layer: every organization, person, service, service area, coating system, preparation method, trust signal, expertise and community involvement record Precision publishes, each with a stable canonical id, aliases, verification status, review metadata and sameAs references. Internal identifiers are never exposed.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum number of entities to return (1-200, default 50).
  • offset · integer · optionnel
    Zero-based offset for pagination.
  • entity_type · string · optionnel · organization | person | service | service_area | coating_system | preparation_method | trust_signal | expertise
    Restrict the result to one public entity type.
  • verification_status · string · optionnel · verified | needs_review | unverified
    Restrict the result to a verification status. Published entities are always `verified`.

  Exemple d'appel

  {"name": "get_public_entities", "arguments": {"limit": 1, "offset": 1, "entity_type": "organization", "verification_status": "verified"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_public_entity≈ 163 tokens

  Returns a single published public entity by canonical id, canonical URI, slug or alias, together with its incoming and outgoing approved relationships and the schema.org JSON-LD node generated from the same record.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Canonical public id (`pcc:service/garage-floor-coatings`), canonical URI, slug or alias.

  Exemple d'appel

  {"name": "get_public_entity", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_record_standards≈ 253 tokens

  Returns the approved standards that a specific Precision knowledge record references, with the relationship predicate (`tested_per`, `guided_by`, `measured_by`, `references`, …) and an applicability summary explaining why the standard is relevant. Answers "what is this practice based on?" with citable provenance.

  Paramètres, retour & exemple (2)

  Paramètres

  • record · string · requis
    Record slug or canonical public entity id (`pcc:preparation-method/diamond-grinding`).
  • record_kind · string · optionnel
    Optional record family filter (`installation_standard`, `inspection_standard`, `failure_analysis`, `warranty_term`, `maintenance_record`, `knowledge_entry`).

  Exemple d'appel

  {"name": "get_record_standards", "arguments": {"record": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_service_areas≈ 92 tokens

  Returns the approved service areas together with the headquarters, primary city, state, county and overall service region.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_service_areas", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_standard≈ 170 tokens

  Returns a single referenced standard by canonical public id, standard number or alias, with its provenance (official source URL, edition, last verified date), lifecycle warnings, supersession chain and the Precision records that reference it.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Canonical public id (`pcc:standard/astm-f2170`), standard number (`ASTM F2170`) or alias.

  Exemple d'appel

  {"name": "get_standard", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_standard_relationships≈ 177 tokens

  Returns the approved edges that connect Precision entities and knowledge records to referenced standards, including the predicate and the applicability summary. Use it to traverse the provenance layer of the knowledge graph.

  Paramètres, retour & exemple (2)

  Paramètres

  • standard · string · optionnel
    Canonical standard id or standard number to centre on.
  • predicate · string · optionnel
    Restrict to one predicate.

  Exemple d'appel

  {"name": "get_standard_relationships", "arguments": {"standard": "texte", "predicate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_standards≈ 328 tokens

  Returns the approved external technical standards Precision's published knowledge references — ASTM, ICRI, ACI, ANSI, OSHA, EPA and manufacturer technical documents. Each record carries the standard number, official title, issuing organization, edition, official source URL, an original scope summary and lifecycle status. Reference metadata only: the text of a standard is never reproduced, and a reference is not a certification or compliance claim.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum number of standards to return (1-200, default 50).
  • topic · string · optionnel
    Restrict to standards tagged with a topic such as `moisture`, `surface-preparation`, `adhesion`, `safety`.
  • lifecycle · string · optionnel · active | superseded | withdrawn
    Restrict to a lifecycle state.
  • organization · string · optionnel
    Restrict to one issuing organization (for example `ASTM`, `ICRI`, `OSHA`).

  Exemple d'appel

  {"name": "get_standards", "arguments": {"limit": 1, "topic": "texte", "lifecycle": "active", "organization": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_warranty≈ 108 tokens

  Returns the approved public warranty knowledge graph: the derived summary plus coverage, exclusions, maintenance requirements, claims process, transfer policy and warranty FAQ records.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_warranty", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• request_appointment_reschedule≈ 697 tokens

  Asks internal JoJo for a different walkthrough time using new preferences. The existing hold stays in place until JoJo replaces it, so a duplicate appointment is never created and the customer is never left without one.

  Paramètres, retour & exemple (7)

  Paramètres

  • reason · string · optionnel
    Why the customer needs a different time.
  • timezone · string · optionnel
    IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago.
  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.
  • new_scheduling_preferences · object · optionnel
    What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly.
  • customer_authorized_reschedule · boolean · requis
    Must be true. The customer asked to reschedule.

  Exemple d'appel

  {"name": "request_appointment_reschedule", "arguments": {"request_id": "texte", "customer_access_token": "texte", "customer_authorized_reschedule": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• request_estimate_appointment≈ 724 tokens

  Asks Precision's internal JoJo scheduler to reserve an authorized on-site walkthrough that fits the customer's stated preferences. The caller never sees or selects calendar availability: JoJo reads the private calendar, applies the preferences and returns exactly one proposed time awaiting customer confirmation. If nothing matches, the response says so and asks for wider preferences.

  Paramètres, retour & exemple (6)

  Paramètres

  • timezone · string · optionnel
    IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago.
  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.
  • scheduling_preferences · object · optionnel
    What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly.
  • customer_authorized_scheduling · boolean · requis
    Must be true. Confirms the customer explicitly asked for an appointment to be scheduled.

  Exemple d'appel

  {"name": "request_estimate_appointment", "arguments": {"request_id": "texte", "customer_access_token": "texte", "customer_authorized_scheduling": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_knowledge≈ 264 tokens

  Full-text style search across every published Approved Knowledge record — company, services, service areas, warranty, installation, inspection, failure-analysis, maintenance and business operations knowledge. Omit the query to receive the full index.

  Paramètres, retour & exemple (3)

  Paramètres

  • q · string · optionnel
    Search terms. When omitted the complete published record index is returned.
  • limit · integer · optionnel
    Maximum number of results (1–50). Defaults to 10.
  • module · string · optionnel · company | services | service_areas | approved_knowledge | warranty | installation_standards | inspection_standards | failure_analysis
    Restrict results to a single knowledge module.

  Exemple d'appel

  {"name": "search_knowledge", "arguments": {"q": "texte", "limit": 1, "module": "company"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_public_entities≈ 280 tokens

  Ranked search over published public entity names, aliases, canonical ids and descriptions. Use it to resolve a free-form mention ("Conroe", "flake floor") to a stable canonical Precision entity id.

  Paramètres, retour & exemple (3)

  Paramètres

  • q · string · requis
    Search text.
  • limit · integer · optionnel
    Maximum number of matches (1-50, default 10).
  • entity_type · string · optionnel · organization | person | service | service_area | coating_system | preparation_method | trust_signal | expertise
    Restrict the search to one public entity type.

  Exemple d'appel

  {"name": "search_public_entities", "arguments": {"q": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_standards≈ 177 tokens

  Ranked search over standard numbers, titles, aliases, topics and scope summaries. Use it to resolve a free-form mention such as "in-situ RH test" or "CSP profile" to the canonical standard Precision references.

  Paramètres, retour & exemple (2)

  Paramètres

  • q · string · requis
    Search text.
  • limit · integer · optionnel
    Maximum matches (1-50, default 10).

  Exemple d'appel

  {"name": "search_standards", "arguments": {"q": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_estimate_for_review≈ 344 tokens

  Submits the request to Precision's internal JoJo review layer and the office, creating or linking the customer record and notifying staff. Every field in required_to_submit must be present first (customer_name, phone, project_city, project_state, project_type, approximate_square_feet, consent_to_contact), along with a contact method and consent. Submitting requests a visit; it does not confirm pricing, scope or a time.

  Paramètres, retour & exemple (4)

  Paramètres

  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_statement · string · optionnel
    The customer's own words for this step, stored verbatim as the evidence trail.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.

  Exemple d'appel

  {"name": "submit_estimate_for_review", "arguments": {"request_id": "texte", "customer_access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_estimate_request≈ 1039 tokens

  Token-scoped update. Adds or corrects customer-provided details on an existing request. Values are validated against the shared schema and every change is audited with the calling channel.

  Paramètres, retour & exemple (6)

  Paramètres

  • updates · object · requis
    The fields to change.
  • request_id · string · requis
    The request_id returned by create_estimate_request.
  • idempotency_key · string · optionnel
    Optional client-supplied key. Repeating a call with the same key never duplicates work.
  • customer_statement · string · optionnel
    The customer's own words for this step, stored verbatim as the evidence trail.
  • customer_access_token · string · requis
    The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.
  • scheduling_preferences · object · optionnel
    What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly.

  Exemple d'appel

  {"name": "update_estimate_request", "arguments": {"updates": {}, "request_id": "texte", "customer_access_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://app.precision-concretecoating.com/api/public/mcp