Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Requisition (Subcontractor Invoice) Contract Detail Item

update_requisition_subcontractor_invoice_contract_detail_item

Update specific fields on a subcontractor invoice requisition's contract detail item, including work completed and retainage amounts. Requires requisition, contract detail item, and project IDs.

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}/contract_detail_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requisition_idYesURL path parameter — requisition (Subcontractor Invoice) ID
idYesURL path parameter — contract Detail 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
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 contract only)
Behavior3/5

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

Discloses that only supplied fields are changed (PATCH semantics) and that the modified object is returned on success. Lacks details on permissions, side effects, or error scenarios. Annotations (destructiveHint=false, readOnlyHint=false) already indicate mutation, so the description adds marginal value.

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?

Three sentences cover deprecation, behavior, and required parameters. The 'Procore API' line adds context but could be trimmed. Overall efficient, though the second sentence repeats schema information.

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?

Covers core purpose and deprecation but does not elaborate on return structure or error conditions. The inconsistency in resource naming ('Commitments' vs. contract detail item) slightly undermines completeness.

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?

Input schema has 100% coverage, so each parameter is already documented. The description merely lists the required parameters (redundant), adding no new meaning beyond the schema.

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 an existing contract detail item and is deprecated, advising use of the bulk endpoint. However, it incorrectly refers to the resource as 'Commitments' instead of 'contract detail item', causing minor confusion.

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?

Explicitly advises against using this endpoint by labeling it deprecated and directing to an alternative ('bulk_item_update'), providing clear guidance on when not to use it.

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