Skip to main content
Glama
TylerIlunga

Procore MCP Server

update_commitment_contract_v2_0

Modify commitment contract details in Procore to update project financials, including status, vendor information, payment terms, and contract specifications.

Instructions

Update Commitment Contract. [Construction Financials/Commitments] PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/commitment_contracts/{commitment_contract_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesUnique identifier for the company.
project_idYesUnique identifier for the project.
commitment_contract_idYesUnique identifier for the Commitment Contract.
viewNoSpecifies which view (which attributes) of the resource is going to be present in the response. The extended view includes vendor name and custom fields data, while the default view does not.
numberNoThe Commitment Contract number. Defaults to the project numbering sequence for the respective contract type.
statusNoThe Commitment Contract status.
titleNoThe Commitment Contract title.
descriptionNoThe Commitment Contract description.
executedNoThe Commitment Contract executed status.
vendor_idNoThe ID of the vendor for the contract. The selected invoice contacts must all belong to this vendor. When the vendor is changed, the invoice contacts are reset.
assignee_idNoOnly applicable to Purchase Order Contracts. The ID of the user assigned to the Commitment Contract. The user must belong to the project directory (see the Project Users endpoint).
signature_requiredNoIf true, a signature is required to execute the contract; otherwise no signature is required.
billing_schedule_of_values_statusNoThe subcontractor schedule of values (SSOV) status. Only applicable to contracts which use an SSOV.
inclusionsNoOnly applicable to Work Order Contracts. The inclusions of the Commitment Contract.
exclusionsNoOnly applicable to Work Order Contracts. The exclusions of the Commitment Contract.
bill_to_addressNoOnly applicable to Purchase Order Contracts. The address to which invoices are sent. The default will be the bill to address of the most recently created purchase order.
ship_to_addressNoOnly applicable to Purchase Order Contracts. The address to which materials are shipped. The default will be the ship to address of the most recently created purchase order.
ship_viaNoOnly applicable to Purchase Order Contracts. The shipping method for the Commitment Contract.
payment_termsNoOnly applicable to Purchase Order Contracts. The payment terms for the Commitment Contract.
retainage_percentNoAn "unformatted" decimal number. Specifically a number with a period as the decimal separator, without a thousands separator, and with an optional sign. It should be assumed that this number includ...
accounting_methodNoThe accounting method for the contract. Default is driven by a project setting.
allow_commentsNoIf true, comments are allowed on the Commitment Contract; otherwise comments are not allowed. Default is driven by a project setting.
allow_markupsNoIf true, markups are allowed on the Commitment Contract; otherwise markups are not allowed. Default is driven by a project setting.
change_order_level_of_detailNoThe level of details for showing change orders on invoices attached to this contract.
enable_ssovNoIf true, the subcontractor schedule of values (SSOV) is enabled for the Commitment Contract; otherwise the SSOV is not enabled. Default is driven by a project setting.
allow_change_orders_ssovNoIf true, the subcontractor schedule of values (SSOV) can be enabled on change orders for this Commitment Contract. When enabled, Change Order SSOV toggles become available. Default is false.
allow_payment_applicationsNoIf true, invoices are allowed on the Commitment Contract; otherwise invoices are not allowed. Default is driven by a project setting.
allow_paymentsNoIf true, payments are allowed on the Commitment Contract; otherwise payments are not allowed. Default is driven by a project setting.
display_materials_retainageNoIf true, materials retainage is displayed on the Commitment Contract; otherwise materials retainage is not displayed. Default is driven by a project setting.
display_work_retainageNoIf true, work retainage is displayed on the Commitment Contract; otherwise work retainage is not displayed. Default is driven by a project setting.
show_cost_code_on_pdfNoIf true, cost codes are displayed on the Commitment Contract PDF; otherwise cost codes are not displayed. Default is driven by a project setting.
ssr_enabledNoIf true, the sliding scale retention is enabled for the Commitment Contract. Default is driven by a project setting.
bill_recipient_idsNoIDs of users in the project directory (see the Project Users endpoint). These users must belong to the selected vendor and are the invoice contacts for submitting subcontractor invoices. To grant a...
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Update' which implies a mutation operation, but provides no information about permissions required, whether changes are reversible, rate limits, or what happens to unspecified fields. The API endpoint path suggests PATCH semantics, but this is insufficient for a mutation tool with 33 parameters and no annotation coverage.

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

Conciseness4/5

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

The description is extremely concise with just one sentence containing the tool purpose, category, and API endpoint. While under-specified for a complex mutation tool, it wastes no words and is front-loaded with the core action. The structure is efficient though incomplete.

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

Completeness2/5

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

For a complex mutation tool with 33 parameters, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what 'update' entails, what fields can be modified, permissions required, or expected response format. The API endpoint path provides some context but doesn't compensate for the missing behavioral and usage information needed for proper tool invocation.

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

Parameters3/5

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

Schema description coverage is 100%, with detailed descriptions for all 33 parameters including enums and applicability notes. The description adds no parameter information beyond what's already in the schema. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no param info in description, which applies here.

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

Purpose2/5

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

The description 'Update Commitment Contract' is a tautology that restates the tool name with minimal additional context. It adds a category '[Construction Financials/Commitments]' and API endpoint path, but lacks a specific verb+resource combination that distinguishes it from sibling tools. While the endpoint path provides some context, the core description is essentially a restatement of the name.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when-not-to-use scenarios, or refer to sibling tools like 'create_commitment_contract_v2_0' or other update-related tools. The agent receives zero usage direction beyond the tool name itself.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TylerIlunga/procore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server