Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Contract Compliance Document

update_contract_compliance_document
Idempotent

Update contract compliance document details in Procore, such as status, dates, or notes, using existing document ID and contract ID.

Instructions

Updates a contract compliance document Procore Pay must be enabled to use this endpoint.. Send only the fields you intend to change; omitted fields keep their current values. company_id and project_id default to the values set by procore_set_config when omitted, and contract_id, id must identify existing parent records — resolve them with the matching list tool first. Returns the modified contract compliance document on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id, project_id, contract_id, id. Procore API (v2.0): Construction Financials > Payments. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/contracts/{contract_id}/documents/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the compliance document
nameNoJSON request body field — name of the compliance document
notesNoJSON request body field — notes for the compliance document. Only commitment admins can update this field.
statusNoJSON request body field — status of the compliance document
company_idYesURL path parameter — unique identifier for the Procore company
expires_atNoJSON request body field — expiration date of the compliance document
project_idYesURL path parameter — unique identifier for the Procore project
contract_idYesURL path parameter — unique identifier of the contract
effective_atNoJSON request body field — effective date of the compliance document
document_typeNoJSON request body field — document type of the compliance document
reviewer_notesNoJSON request body field — notes from the reviewer
prostore_file_idsNoJSON request body field — array of Procore file IDs
allow_vendor_submissionNoJSON request body field — whether vendors are allowed to submit this compliance document
send_expiration_notificationNoJSON request body field — whether an expiration notification should be sent before this compliance document expires. Only commitment admins can update this field.
Behavior5/5

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

Beyond annotations (readOnlyHint false, destructiveHint false), the description discloses crucial behavioral traits: the Procore Pay requirement, partial update behavior, ID defaulting, prerequisite resolution via list tools, and success/error payloads. This is rich, actionable context that annotations alone do not provide.

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

Conciseness5/5

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

The description is dense but well-structured: action and prerequisite in the first sentence, then partial-update semantics, defaulting, prerequisite resolution, return value, error handling, and endpoint. Every sentence serves a purpose, and the length is justified for a 14-parameter PATCH endpoint.

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

Completeness5/5

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

With no output schema, the description appropriately states the success return ('Returns the modified contract compliance document'). It also covers prerequisites, defaults, error responses, and endpoint location. For a complex tool with 14 parameters, this description is remarkably complete.

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

Parameters4/5

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

Input schema already documents all 14 parameters with 100% coverage. The description adds essential semantics by clarifying that omitted fields retain current values, which is fundamental to understanding how to use the update parameters. It also reiterates required parameters (company_id, project_id, contract_id, id), adding value beyond the schema.

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

Purpose5/5

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

The description opens with 'Updates a contract compliance document', clearly stating the verb and resource. It further specifies the endpoint and scope (PATCH /rest/v2.0/.../compliance/contracts/{contract_id}/documents/{id}), distinguishing it from sibling tools like create and get contract compliance documents.

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

Usage Guidelines5/5

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

Provides explicit usage guidance: 'Send only the fields you intend to change; omitted fields keep their current values' clarifies partial update semantics. It also instructs to resolve parent records with the matching list tool first, and explains defaulting of company_id/project_id from procore_set_config. Error handling guidance (401/403/404) further helps the agent decide when and how to use the tool.

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