Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Work Order Contract

update_work_order_contract

Update a Work Order Contract by providing its ID, project ID, and the contract fields to modify. Only specified fields are changed.

Instructions

Update a specified Work Order Contract. Use this to update an existing Commitments (only the supplied fields are changed). Updates the specified Commitments and returns the modified object on success. Required parameters: id, project_id, work_order_contract. Procore API: Construction Financials > Commitments. Endpoint: PATCH /rest/v1.0/work_order_contracts/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Commitments resource
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
project_idYesJSON request body field — unique identifier for the project.
attachmentsNoJSON request body field — work Order Contract attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]`...
work_order_contractYesJSON request body field — work Order Contract object
Behavior4/5

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

Beyond annotations (readOnlyHint false, destructiveHint false, idempotentHint false, openWorldHint true), the description adds that only supplied fields are changed (partial update) and that the modified object is returned. This adds valuable behavioral context.

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 very concise (3 sentences) and front-loaded with the action. It includes the required parameters and API endpoint, making it efficient and clear.

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

Completeness4/5

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

Given the 5 parameters, nested object, and no output schema, the description covers the essential: what it does, what to provide, and what to expect (modified object). It is complete enough for an agent to use correctly.

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?

The input schema has 100% description coverage, so the description's mention of required parameters adds little new information. It does note that only supplied fields are changed, which relates to the work_order_contract object.

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

Purpose4/5

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

The description clearly states the tool updates a Work Order Contract ('Update a specified Work Order Contract'), using the verb 'Update' and the resource. It mentions 'Commitments' but doesn't explicitly differentiate from sibling tools like update_commitment_contract or update_purchase_order_contract.

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

Usage Guidelines3/5

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

The description says to use it for updating existing Commitments and lists required parameters. However, it does not provide guidance on when not to use it or suggest alternatives, which is important given the many sibling contract-related tools.

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