Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Requisition (Subcontractor Invoice) Change Order Item

update_requisition_subcontractor_invoice_change_order_item

Update work completed, materials stored, and retainage fields on a change order item for a subcontractor invoice.

Instructions

This is a deprecated endpoint, please use /rest/v1.0/requisitions/{requisition_id}/bulk_item_update. 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: requisition_id, id, project_id. Procore API: Construction Financials > Commitments. Endpoint: PATCH /rest/v1.0/requisitions/{requisition_id}/change_order_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requisition_idYesURL path parameter — requisition (Subcontractor Invoice) ID
idYesURL path parameter — change Order Item ID
project_idYesQuery string parameter — unique identifier for the project.
work_completed_this_periodNoJSON request body field — the amount of work completed this period
materials_presently_storedNoJSON request body field — the amount of materials presently stored (amount accounting only)
work_completed_retainage_retained_this_periodNoJSON request body field — work completed retainage amount retained this period (admin user only, work_completed_this_period should be non-zero to hold a retainage)
materials_stored_retainage_currently_retainedNoJSON request body field — materials stored retainage amount currently retained (admin user, amount accounting only, materials_presently_stored should be non-zero to hold a retainage)
work_completed_retainage_released_this_periodNoJSON request body field — the amount of work completed retainage released this period
work_completed_this_period_quantityNoJSON request body field — work completed this period quantity (unit accounting only)
Behavior4/5

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

The description clarifies that only supplied fields are changed (partial update) and that the modified object is returned. This adds useful behavioral context beyond the annotations, which already indicate modification (readOnlyHint=false) and non-destructiveness (destructiveHint=false).

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

Conciseness3/5

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

The description contains several sentences including a deprecation warning, action statement, parameter list, and API reference. While each part serves a purpose, the structure is somewhat disjointed and could be more streamlined.

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

Completeness3/5

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

The tool has 9 parameters and no output schema. The description states that the response is the modified object but does not describe its structure or provide examples. It lacks explanation of what a change order item is within the requisition context, leaving some gaps for effective agent usage.

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?

All 9 parameters are fully described in the input schema (100% coverage). The description lists the three required parameters, but this duplicates schema information and adds no additional semantic meaning beyond what the schema already provides.

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 states it is deprecated and directs users to a bulk update endpoint. It says 'update an existing Commitments' but the tool name and input schema refer to a 'change order item,' creating confusion about the resource being modified.

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 explicitly advises against using this tool by directing to the bulk update endpoint. However, it does not explain when to use this tool over the alternative or describe any specific context where the deprecated endpoint might still be needed.

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