RetailHardHat's MCP server lets an assistant work with an organization's retail sites, projects, budgets, bids, permits and field work, including an interactive operations dashboard. An organization admin grants modules and read-only or guarded-write access; sensitive writes need human review by default.
Scored across 440 tools
While many tools are cleanly scoped to one resource+action, there are clusters of near-synonyms that an agent will routinely misselect: find_budget_approval_request vs get_budget_approval_request vs get_budget_approval, submit_budget_approval_request vs submit_budget_for_approval, and get_operations_dashboard vs render_retailhardhat_dashboard vs render_retailhardhat_view. The per-entity document quartet (attach_/read_/update_/delete_ X_document) across eight entities adds heavy surface where the only differentiator is a noun buried mid-name, and at 440 tools the sheer selection space guarantees collisions even where descriptions are precise.
The dominant pattern is verb_noun (list_sites, create_bid, delete_permit, apply_task_template), which is good. But noun number is inconsistent (list_sites vs list_milestone, list_criteria_profile, list_pipeline_stage, list_approval_flow), and verbs are mixed across synonyms (find_ vs get_ vs list_, submit_for_approval vs submit_..._approval_request). Readable, but not a predictable grammar an agent can rely on.
440 tools for a retail construction/real-estate platform is a severe mismatch with what an agent can meaningfully navigate or select well. Large families are mechanically expanded (budget templates, project/site/task templates, eight document entity variants, webhooks, integrations), inflating the surface far beyond any realistic task scope.
Domain coverage is genuinely broad — CRUD plus templates, approvals, attachments, reporting, notifications, and integrations are all present, so few workflows dead-end. However, completeness is undermined by fragmentation: the same concept is spread across find/get/submit/decide/cancel variants and there is little bulk or search-oriented tooling outside a few budget-specific cases, forcing long tool chains.
activate an investment criteria profile. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Configure a budget approver, not an approval decision. Organization admin required. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Assign an existing organization user to a project, with an optional project role. Does not create an account or change organization permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), projectId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Append an item to a purchase template. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), templateId (required). Returns: data
Assign an existing organization user to a site team. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Apply a budget template to an existing site. Does not create the destination. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Apply checklist items to a site's active checklist; existing titles are deduplicated. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Apply a folder across the organization's sites. Broad sharing/organization change: review the source folder first. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: folderId (required). Returns: data
Apply a project_budget template to an existing project. Does not create the destination. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Apply a project_task template to an existing project. Does not create the destination. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Apply a template to a site's purchase list. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Apply a task template to an existing site. Does not create the destination. data.anchorDate is required; use the user's requested anchor or today's local date when unspecified and disclose the anchor in the preview. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
archive an investment criteria profile. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a bid. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), bidId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a change_request. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), changeRequestId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Attach an owned uploaded closeout document; cannot self-approve it. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Attach an owned uploaded photo to a daily log. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), dailyLogId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a permit. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), permitId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a project. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), projectId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a rfp. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), rfpId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a site. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Attach an uploaded file owned by this organization to a task. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), taskId (required). Returns: data
Attach an organization-owned uploaded file to a utility connection. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), utilityConnectionId (required). Returns: data
Assign or unassign up to 25 budget lines to an existing organization user. All rows must be editable; no silent skips. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Cancel your own pending bid approval request; cannot cancel another submitter's request. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Cancel your own pending budget approval request; cannot cancel another submitter's request. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Cancel your own pending invoice approval request; cannot cancel another submitter's request. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Cancel your own pending rfp approval request; cannot cancel another submitter's request. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Clone a budget template with its items. Rename the returned template using its actual ID in a dependent step. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when comparing recorded contractor bids for a RetailHardHat location UUID. Groups by category, project, and RFP; shows amounts and differences from each group's lowest eligible amount. Do not use for unrelated insurance quotes or automatically select, approve, or award a contractor.
Inputs: siteId (required). Returns: data
Create approval_flow using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add an approval flow step. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), flowId (required). Returns: data
Create assignment_automation using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat bids records in the connected organization. Create bid. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Create an organization budget category, optionally with an explicit stable key for dependent template items. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Create a budget line item. Requires financial approval. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), budgetId (required). Returns: data
Create a reusable budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add an item to a budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Create a change request. Author is derived from the connection. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Add a financial change-request line item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), changeRequestId (required). Returns: data
Add a site checklist item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), checklistId (required). Returns: data
Create checklist_template using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add a checklist template item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat contacts records in the connected organization. Create a contact. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create/link this site's location in the existing credentialcamp connection. Review all transmitted fields; external system changes are not automatically rolled back. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create criteria_profile using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create a location custom field, including its dropdown options. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create custom_role using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Create a field log with author derived from the connection. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Use this when working with RetailHardHat deals records in the connected organization. Create deal. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Create a draft deal budget; existing current-budget rules still apply. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), dealId (required). Returns: data
Create diligence_field using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create diligence_tab using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Create a folder in a site's document tree. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Create/link this site's location in the existing incidentvault connection. Review all transmitted fields; external system changes are not automatically rolled back. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Create a bid invoice. Does not execute payment or mark it paid. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), bidId (required). Returns: data
Create/link this site's location in the existing leasecommand connection. Review all transmitted fields; external system changes are not automatically rolled back. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create milestone using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create milestone_column using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create an organization webhook. Sends future selected event data to the reviewed HTTPS endpoint; signing secret is not exposed to AI. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat permits records in the connected organization. Create permit. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create phase using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create pipeline_stage using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create/link this site's location in the existing policytrak connection. Review all transmitted fields; external system changes are not automatically rolled back. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Create project. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Create a project budget item. Requires financial approval. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), projectId (required). Returns: data
Create a reusable project_budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add an item to a project_budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Add a project note. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), projectId (required). Returns: data
create a general-project task, not a site task. Supports hierarchy, assignment, status, priority and due dates; no completion timestamp or actor overrides. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), projectId (required). Returns: data
Create a reusable project_task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add an item to a project_task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Create a punch-list item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Add an item to a site's purchase list. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Create a purchase template. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Create/link this site's location in the existing quipassist connection. Review all transmitted fields; external system changes are not automatically rolled back. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat rfis records in the connected organization. Create rfi. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add a rfi comment as the current user; author and mentions remain server-owned. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), rfiId (required). Returns: data
Use this when working with RetailHardHat rfps records in the connected organization. Create rfp. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Save a report using the report registry's exact dataset and column definitions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat sites records in the connected organization. Create site. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Create a draft site budget; existing current-budget rules still apply. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Build/add budget items from this site's approved contracts through the existing screen service. Review the contracts first; may affect multiple items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
Create/link this site's location in the existing smartshifts connection. Review all transmitted fields; external system changes are not automatically rolled back. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add a Target Location / target market / desired expansion city. Only market is required; no site, deal or street address is needed. Other fields use screen defaults. Organization admin required. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat tasks records in the connected organization. Create task. Required fields are validated by the application. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add a task comment as the current user; author and mentions remain server-owned. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), taskId (required). Returns: data
Create a real dependency; existing cycle and relationship validation applies. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), taskId (required). Returns: data
Create a reusable task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Add an item to a task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Create team_assignment_automation using the same business service as the screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Create a utility provider. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Create a utility connection. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required). Returns: data
Use this when working with RetailHardHat vendors records in the connected organization. Create vendor. Required fields are validated by the application. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Record the current human user's explicit approve/reject decision for a bid. Requires exact-change review and being an assigned current-step approver. Amount ceilings restrict approvals, not rejections; subsequent approval steps still apply. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), requestId (required). Returns: data
Record the current human user's explicit approve/reject decision for a budget. Requires exact-change review and being an assigned current-step approver. Amount ceilings restrict approvals, not rejections; subsequent approval steps still apply. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), requestId (required). Returns: data
Record the current human user's explicit approve/reject decision for a invoice. Requires exact-change review and being an assigned current-step approver. Amount ceilings restrict approvals, not rejections; subsequent approval steps still apply. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), requestId (required). Returns: data
Record the current human user's explicit approve/reject decision for a rfp. Requires exact-change review and being an assigned current-step approver. Amount ceilings restrict approvals, not rejections; subsequent approval steps still apply. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), requestId (required). Returns: data
Delete approval_flow. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete assignment_automation. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat bids records in the connected organization. Delete bid. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a bid document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: bidId (required), documentId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Delete a draft budget and its dependent records. No force override. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Remove a custom budget category; application safeguards still apply. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: categoryId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Delete a budget line item. Requires financial approval. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete a budget template and its normal dependent records. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove an item from a budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), itemId (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Delete a change request and dependent records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a change_request document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required), changeRequestId (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Remove a financial change-request line item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required), changeRequestLineItemId (required). Returns: data
Delete checklist_item. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete checklist_template. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete checklist_template_item. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Delete a closeout document. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: closeoutDocumentId (required). Returns: data
Use this when working with RetailHardHat contacts records in the connected organization. Delete a contact. Requires organization administrator permissions. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: contactId (required). Returns: data
Delete criteria_profile. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove a custom field and clear its stored values. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete custom_role. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Delete a daily log and dependent media records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: dailyLogId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Delete a daily-log photo through the application's normal route. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: mediaId (required), dailyLogId (required). Returns: data
Use this when working with RetailHardHat deals records in the connected organization. Delete deal. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete diligence_field. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete diligence_tab. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Delete a folder using existing nonempty-folder safeguards. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: folderId (required). Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Delete an invoice record and its normal associations. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: bidId (required), invoiceId (required). Returns: data
Delete milestone. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete milestone_column. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove an organization webhook. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat permits records in the connected organization. Delete permit. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a permit document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: permitId (required), documentId (required). Returns: data
Delete phase. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete pipeline_stage. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Delete project. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Delete a project budget item. Requires financial approval. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: itemId (required), projectId (required). Returns: data
Delete a project_budget template and its normal dependent records. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove an item from a project_budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), itemId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a project document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required), documentId (required). Returns: data
delete an existing project note's title/content. The original author and project cannot be changed. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: noteId (required), projectId (required). Returns: data
delete a general-project task, not a site task. Supports hierarchy, assignment, status, priority and due dates; no completion timestamp or actor overrides. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required), projectTaskId (required). Returns: data
Delete a project_task template and its normal dependent records. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove an item from a project_task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), itemId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Delete a punch-list item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: punchItemId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Delete a purchase item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), purchaseItemId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Delete a purchase template and its items. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: templateId (required). Returns: data
Use this when working with RetailHardHat rfis records in the connected organization. Delete rfi. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete your own rfi comment. Cannot impersonate another author. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: rfiId (required), commentId (required). Returns: data
Use this when working with RetailHardHat rfps records in the connected organization. Delete rfp. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a rfp document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: rfpId (required), documentId (required). Returns: data
Delete a saved report. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat sites records in the connected organization. Delete site. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a site document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), documentId (required). Returns: data
Delete a desired Target Location / expansion market, not a site. Organization admin and an exact reviewed preview are required. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat tasks records in the connected organization. Delete task. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Delete your own task comment. Cannot impersonate another author. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), commentId (required). Returns: data
Remove a task dependency. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), dependencyId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Remove a task document using the application's normal file-deletion rules. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), documentId (required). Returns: data
Delete a task template and its normal dependent records. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove an item from a task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), itemId (required). Returns: data
Delete team_assignment_automation. Review dependent-record effects before confirming. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Delete a utility provider. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: utilityCompanyId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Delete a utility connection. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: utilityConnectionId (required). Returns: data
Delete a specific attached utility document and its stored file after review. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: storageKey (required), utilityConnectionId (required). Returns: data
Use this when working with RetailHardHat vendors records in the connected organization. Delete vendor. Subject to configured MCP approval rules; may cascade to related records. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Dismiss one of your own notifications. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Duplicate a budget and its line items as a new version. Does not approve the copy. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required), data. Returns: data
Execute a human-approved action once. Arguments are loaded from the immutable approval, never supplied again. Failed or executing actions cannot be retried automatically.
Inputs: approvalId (required).
Export an authorized report as CSV, Excel XLSX or PDF. Discover datasets with get_report_registry first. Returns a downloadable MCP embedded file, never a public or signed URL. allPages reads up to maxRows (default 500, hard cap 1000 or a lower organization/connection policy). Always disclose truncation. Every page rechecks permissions and masking. Requires explicit export permission. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: args (required), name (required), format, maxRows, +1 more. Returns: data
Read the existing business approval request for a bid. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: entityId (required), entityType. Returns: data
Read the existing business approval request for a budget. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: entityId (required), entityType. Returns: data
Read the existing business approval request for a invoice. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: entityId (required), entityType. Returns: data
Read the existing business approval request for a rfp. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: entityId (required), entityType. Returns: data
Read a approval_flow record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read the status of an approval belonging to this connection.
Inputs: approvalId (required).
Read a bid approval request, its steps and actions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Use this to inspect a recorded RetailHardHat contractor bid's scope, amount, status and notes before making a comparison. Requires the bid's real UUID. Never approves, selects or awards the bid.
Inputs: bidId (required). Returns: data
Use this when working with RetailHardHat reports records in the connected organization. Read organization reporting data; no platform-level analytics. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read a whole budget. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Read a budget's approval request and progress without making an approval decision. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Read a budget approval request, its steps and actions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Use this to explain which actual budget line items contribute to a RetailHardHat source/category total or overrun. Read-only drill-down of the current authorized portfolio; distinguishes missing actuals from zero and does not combine overlapping sources.
Inputs: category (required), sourceId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read committed budget amounts. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read budget change history. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Read linked task counts for a budget's line items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read current portfolio budgets and normalized category line items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read a budget template and its configuration. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Read a change request. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Read change-request budget-impact. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required). Returns: data
Read a checklist_template record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read a closeout document record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: closeoutDocumentId (required). Returns: data
Use this when identifying which RetailHardHat account and organization are connected. Reads only the authenticated actor's account label, organization, role, and permitted modules. Do not use to enumerate users or change account permissions.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat contacts records in the connected organization. Read an organization contact. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: contactId (required). Returns: data
Read credentialcamp integration status without credentials. Configure credentials through the secure settings screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read a criteria_profile record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a custom_role record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read a daily log and its media. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: dailyLogId (required). Returns: data
Use this when working with RetailHardHat deals records in the connected organization. Read a deal by ID. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a document folder before changing its organization-wide scope. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: folderId (required). Returns: data
Read vendor portal visibility. Sharing changes require explicit review. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: folderId (required). Returns: data
Read incidentvault integration status without credentials. Configure credentials through the secure settings screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read a invoice approval request, its steps and actions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Get a short-lived download link for an invoice attachment. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: invoiceId (required). Returns: data
Read leasecommand integration status without credentials. Configure credentials through the secure settings screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat leases records in the connected organization. Check whether LeaseCommand synchronization is configured; does not reveal credentials. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read a milestone record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read the organization milestone matrix, optionally for one task template, including site and column identifiers. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, templateId. Returns: data
Read your own notification preferences. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this to inspect the authorized location, task or permit behind a RetailHardHat opening-risk signal. Requires the selected record's corresponding module scope and current route permissions. It is read-only and does not certify readiness or grant access to other modules.
Inputs: id (required), recordType (required). Returns: data
Use this to review RetailHardHat retail-rollout operations in one place: budget overruns, opening risks, contractor bids for a selected location, and this connection's pending approvals. Returns authorized panels, selectable locations, drill-down actions and explicit per-panel errors. Never infers access to ungranted modules, complete readiness or financial forecasts.
Inputs: siteId. Returns: data
Read organization configuration. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read organization webhook configuration, excluding secrets. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat permits records in the connected organization. Read a permit by ID. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a phase record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read policytrak integration status without credentials. Configure credentials through the secure settings screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Read a project by ID. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a project_budget template and its configuration. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a project_task template and its configuration. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read a punch-list item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: punchItemId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Read a purchase template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: templateId (required). Returns: data
Read quipassist integration status without credentials. Configure credentials through the secure settings screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat reports records in the connected organization. Read organization reporting data; no platform-level analytics. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Discover exact supported report datasets, columns and filters before creating or running a report. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat rfis records in the connected organization. Read a rfi by ID. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a rfp approval request, its steps and actions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: requestId (required). Returns: data
Read a saved report definition. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat sites records in the connected organization. Read a site by ID. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Read a location's custom values. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
Read vendor portal visibility. Sharing changes require explicit review. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), documentId (required). Returns: data
Use this when working with RetailHardHat leases records in the connected organization. Read synchronized lease activity and refresh metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
Read smartshifts integration status without credentials. Configure credentials through the secure settings screen. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read a task template and its configuration. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat reports records in the connected organization. Read organization reporting data; no platform-level analytics. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read a team_assignment_automation record. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read a utility connection. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: utilityConnectionId (required). Returns: data
Use this when working with RetailHardHat vendors records in the connected organization. Read a vendor by ID. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when checking which RetailHardHat locations have store-opening risk signals: overdue incomplete site tasks, rejected permits, or expired permits. Requires sites, tasks, and permits scopes. Do not treat results as a critical-path prediction or certification of readiness.
Inputs: siteId. Returns: data
Invite a user by email through the normal invitation workflow. Never creates a password. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Invite a person by email as an organization member or admin. Sends a real email and grants the reviewed role upon acceptance. Replaces a prior pending invitation for that email. Cannot grant platform privileges. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
link a site task and a budget line item from the same site. Does not change budget amounts or approve the budget. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), taskId (required). Returns: data
Read approval flow with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read assignment automation with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read bid document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: bidId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Read invoices for a bid. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: bidId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat bids records in the connected organization. List bids in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Read default or deal-specific budget approvers. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, dealId, offset, +1 more. Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. List your organization's budget line-item categories. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read the line items for a budget. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Read tasks linked to a budget line item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: lineItemId (required), id, limit, offset. Returns: data
Read all items in a budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), limit, offset, search. Returns: data
Find budget templates. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read calendar events in an explicit date range. Omitted dates default to the current UTC calendar month; use explicit dates for the user's local reporting window. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: end, start. Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Read change-request approvals. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read change_request document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Read change-request line-items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: changeRequestId (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Read change requests. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search, siteId. Returns: data
Read checklist items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: checklistId (required). Returns: data
Read checklist template with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read checklist template items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read closeout document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat contacts records in the connected organization. Search organization contacts. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read criteria profile with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read the organization's location custom field definitions and option sets. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read custom role with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read field daily logs, including attached photo metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat deals records in the connected organization. List deals in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Read diligence field with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read diligence tab with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read site document folders. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. List construction invoices, not platform billing invoices. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read LeaseCommand synchronization webhook outcomes. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +1 more. Returns: data
Read milestone with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read milestone column with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read your own notification inbox. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search. Returns: data
Read organization users for assignments. Sensitive account fields are redacted. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read webhook delivery outcomes with secrets redacted. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: webhookId (required), id, limit, offset, +1 more. Returns: data
List organization webhooks without signing secrets. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search. Returns: data
Read business approval requests assigned to the current user's inbox; does not decide or impersonate another approver. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset. Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read permit document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: permitId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat permits records in the connected organization. List permits in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Read phase with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read pipeline stage with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read a project's budget line items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required). Returns: data
Read all items in a project_budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), limit, offset, search. Returns: data
Find project budget templates. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read project document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Read a project's notes. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required), id, limit, offset. Returns: data
Use this when working with RetailHardHat projects records in the connected organization. List projects in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Read tasks on a general project. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required), id, limit, offset. Returns: data
Read all items in a project_task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), limit, offset, search. Returns: data
Find project task templates. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
List this project's team memberships and roles. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: projectId (required), id, limit, offset. Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read site punch-list items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Read a site's purchase list. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search, +1 more. Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Read template line items. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: templateId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Read reusable purchase-list templates. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Read carrier tracking history. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), purchaseItemId (required). Returns: data
Read rfi comments. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: rfiId (required), id, limit, offset, +1 more. Returns: data
Use this when working with RetailHardHat rfis records in the connected organization. List rfis in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read rfp document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: rfpId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat rfps records in the connected organization. List rfps in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Find saved report definitions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Read budgets for a site. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
Read site opening checklists. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read site document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Read invoices for a site. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat leases records in the connected organization. Read synchronized leases. LeaseCommand remains the authoritative source. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
Use this when working with RetailHardHat sites records in the connected organization. List sites in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Read a site's assigned team. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required). Returns: data
List/search Target Locations: desired expansion markets and target cities shared with brokers, not existing sites or the Target retail brand. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search. Returns: data
Read budget line items linked to a site task. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), id, limit, offset. Returns: data
Read direct subtasks of an authorized task. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required). Returns: data
Read task comments. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), id, limit, offset, +1 more. Returns: data
Read predecessor dependencies including date effects and offsets. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required). Returns: data
Read following task dependencies including date effects and offsets. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read task document metadata. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat tasks records in the connected organization. List tasks in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Read all items in a task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), limit, offset, search. Returns: data
Find task templates. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Read team assignment automation with your account's permissions. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
List pending organization team invitations. Invitation tokens and acceptance links are never exposed to AI. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset. Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read organization utility providers. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: limit, offset, search. Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Read utility connections at a site. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Read invoices for a vendor. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: vendorId (required), limit, offset, search. Returns: data
Use this when working with RetailHardHat vendors records in the connected organization. List vendors in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id, limit, offset, search, +2 more. Returns: data
Mark your own notification inbox read. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Mark read one of your own notifications. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Move a site document into a folder, or null for the root. Confidential access and same-site relationships are enforced. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), documentId (required). Returns: data
Read the incidentvault synchronization preview before authorizing external changes. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read the leasecommand synchronization preview before authorizing external changes. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read the policytrak synchronization preview before authorizing external changes. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Read the quipassist synchronization preview before authorizing external changes. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
reactivate a user through the existing account workflow. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized bid file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized change_request file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized permit file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized project file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized rfp file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized site file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Read authorized task file bytes as base64, or UTF-8 text for text files. Maximum 2 MiB. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: documentId (required). Returns: data
Use this when working with RetailHardHat leases records in the connected organization. Refresh this organization's mapped sites from LeaseCommand. Requires an existing integration and human approval; does not edit the source leases. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Refresh tracking using configured carrier integrations. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), purchaseItemId (required). Returns: data
Remove a budget approver after exact-change review. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Remove this exact project membership, not the user's organization account. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: memberId (required), projectId (required). Returns: data
Remove a site team assignment. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), memberId (required). Returns: data
Use this when the user requests an interactive RetailHardHat operations dashboard inside their AI assistant. Supports location selection, panel navigation, refresh, searchable records and read-only detail views. Provider enhancements are capability-dependent. Unsupported hosts receive the same complete structured/text dashboard. Sensitive approvals remain in RetailHardHat.
Inputs: siteId. Returns: data
Use this when the user wants an interactive RetailHardHat budget, opening-risk, contractor-bid, or pending-action view. Prefer the matching summary tool for analysis without UI. Re-fetches authorized records; never accepts model-invented financial values. bid_comparison requires a location UUID. Hosts without MCP Apps still receive full structured/text results.
Inputs: workflow (required), siteId. Returns: data
Change an existing budget approver's order. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Reorder up to 25 existing items in one budget. All item relationships are checked before execution. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), budgetId (required). Returns: data
Set milestone column display order. Organization admin only; all selected columns must belong to this organization. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Reorder phase records. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Reorder pipeline_stage records. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Replace ALL items in a purchase template; an empty array clears them. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), templateId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Request an approved 15-minute upload ticket. PUT the exact bytes to uploadURL, then attach the returned key. Never send base64 bytes in this call. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Resend a pending team invitation email and extend its expiry by seven days. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: invitationId (required). Returns: data
Retry one existing LeaseCommand sync event; does not forge a provider event. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Revoke a pending team invitation; does not delete an existing user. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: invitationId (required). Returns: data
Run a bounded read-only report. Consult get_report_registry for the exact request shape. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Select the current budget for its deal. For a site-only budget use set_current_site_budget. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required). Returns: data
Select a site's current budget after checking it belongs to that site. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: siteId (required), budgetId (required). Returns: data
Change vendor portal visibility. Sharing changes require explicit review. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), folderId (required). Returns: data
Set a defined custom field value on a site. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), fieldId (required). Returns: data
Change vendor portal visibility. Sharing changes require explicit review. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), documentId (required). Returns: data
Submit an existing bid to the configured business approval flow. Does not approve it. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Submit an existing budget to the configured business approval flow. Does not approve it. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Submit a budget to its existing human approval workflow. This does not approve it. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: budgetId (required), data. Returns: data
Submit an existing invoice to the configured business approval flow. Does not approve it. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Submit an existing rfp to the configured business approval flow. Does not approve it. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Use this when reviewing RetailHardHat store-development budgets, category cost breakdowns, or recorded actual-versus-estimated overruns. Returns source-separated category totals and unknown-actual warnings. Do not use for personal finance, new estimates, forecasts, or committed-cost accounting.
Inputs: siteId. Returns: data
Use this when checking this RetailHardHat AI connection's unexpired pending or human-approved actions. This read-only summary never approves or executes anything. Do not use for another user's connection or claim an approved action has already run.
Inputs: no named parameters. Returns: data
suspend a user through the existing account workflow. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
Synchronize a budget line from its linked bid; locked/approved budget restrictions remain effective. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: lineItemId (required). Returns: data
Synchronize organization locations to incidentvault using its configured connection. Review the sync preview first. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Synchronize organization locations to policytrak using its configured connection. Review the sync preview first. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Synchronize organization locations to quipassist using its configured connection. Review the sync preview first. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: no named parameters. Returns: data
Send an explicit test delivery to the configured webhook; review destination first. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required). Returns: data
unlink a site task and a budget line item from the same site. Does not change budget amounts or approve the budget. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: taskId (required), lineItemId (required). Returns: data
Configure/edit approval_flow; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit assignment_automation; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat bids records in the connected organization. Update allowed fields of bid. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Edit bid document metadata; cannot replace its storage identity. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), bidId (required), documentId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Edit a draft budget; cannot bypass approved/locked restrictions. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), budgetId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Rename or organize a budget category without changing its stable key. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), categoryId (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Edit a budget line item. Requires financial approval. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit a budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit a budget template item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required), itemId (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Edit the request without bypassing its business approval workflow. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), changeRequestId (required). Returns: data
Use this when working with RetailHardHat change_requests records in the connected organization. Edit a financial change-request line item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), changeRequestId (required), changeRequestLineItemId (required). Returns: data
Configure/edit checklist_item; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit checklist_template; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit checklist_template_item; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Edit closeout metadata without approval or identity overrides. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), closeoutDocumentId (required). Returns: data
Use this when working with RetailHardHat contacts records in the connected organization. Edit contact details. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), contactId (required). Returns: data
Configure/edit criteria_profile; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit a location custom field and its options. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit custom_role; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Edit a field daily log. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), dailyLogId (required). Returns: data
Use this when working with RetailHardHat deals records in the connected organization. Update allowed fields of deal. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit diligence_field; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit diligence_tab; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Rename a document folder. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), folderId (required). Returns: data
Use this when working with RetailHardHat invoices records in the connected organization. Edit invoice details and attachments without payment/status overrides. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), bidId (required), invoiceId (required). Returns: data
Configure/edit milestone; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit milestone_column; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure your own notification preferences. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Update organization business details; credentials, billing and security controls are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required). Returns: data
Configure an existing user's role, team and authorized settings. The screen's self-role and ownership protections remain in force. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Change an organization webhook's endpoint, events or enabled state. No credential editing. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat permits records in the connected organization. Update allowed fields of permit. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Edit permit document metadata; cannot replace its storage identity. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), permitId (required), documentId (required). Returns: data
Configure/edit phase; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Configure/edit pipeline_stage; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat projects records in the connected organization. Update allowed fields of project. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat budgets records in the connected organization. Update a project budget item. Requires financial approval. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), itemId (required), projectId (required). Returns: data
Edit a project_budget template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit a project_budget template item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required), itemId (required). Returns: data
update an existing project note's title/content. The original author and project cannot be changed. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), noteId (required), projectId (required). Returns: data
update a general-project task, not a site task. Supports hierarchy, assignment, status, priority and due dates; no completion timestamp or actor overrides. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), projectId (required), projectTaskId (required). Returns: data
Edit a project_task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit a project_task template item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required), itemId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Edit a punch-list item without verifier-identity overrides. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), punchItemId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Update a purchase item. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), purchaseItemId (required). Returns: data
Use this when working with RetailHardHat purchase_lists records in the connected organization. Edit a purchase template. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), templateId (required). Returns: data
Use this when working with RetailHardHat rfis records in the connected organization. Update allowed fields of rfi. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit your own rfi comment. Cannot impersonate another author. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), rfiId (required), commentId (required). Returns: data
Use this when working with RetailHardHat rfps records in the connected organization. Update allowed fields of rfp. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Edit rfp document metadata; cannot replace its storage identity. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), rfpId (required), documentId (required). Returns: data
Edit a saved report definition. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat sites records in the connected organization. Update allowed fields of site. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Edit site document metadata; cannot replace its storage identity. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), documentId (required). Returns: data
Set a site's milestone status, target date or actual date. Column can be a real milestone column or a template phase task. Completing a phase also completes its child tasks through the existing screen service; review that consequence. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), columnId (required). Returns: data
Edit a site team member's assignment. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), siteId (required), memberId (required). Returns: data
Edit a Target Location's market, state, priority, radiusMiles, notes or active/paused/filled status. Organization admin required. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat tasks records in the connected organization. Update allowed fields of task. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit your own task comment. Cannot impersonate another author. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), taskId (required), commentId (required). Returns: data
Use this when working with RetailHardHat documents records in the connected organization. Edit task document metadata; cannot replace its storage identity. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), taskId (required), documentId (required). Returns: data
Edit a task template. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Edit a task template item. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required), itemId (required). Returns: data
Configure/edit team_assignment_automation; server-owned fields are excluded. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Edit a utility provider. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), utilityCompanyId (required). Returns: data
Use this when working with RetailHardHat field_operations records in the connected organization. Edit a utility connection. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: data (required), utilityConnectionId (required). Returns: data
Use this when working with RetailHardHat vendors records in the connected organization. Update allowed fields of vendor. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.
Inputs: id (required), data (required). Returns: data
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.