Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Requisition (Subcontractor Invoice)

update_requisition_subcontractor_invoice

Update a subcontractor invoice (requisition) in Procore, with role-based access: admins any status, others only draft or revise_and_resubmit.

Instructions

Update a specified Requisition (Subcontractor Invoice). Users without admin permissions can only update a requisition (sub invoice) if it is the most recent and has a status of 'draft' or 'revise_and_resubmit'. Users with admin permissions can update a requisition (sub invoice) regardless of its status or whether it is the most recent. Requisition items are optional. 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, commitment_id. Procore API (v1.1): Construction Financials > Commitments. Endpoint: PATCH /rest/v1.1/requisitions/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — requisition (Subcontractor Invoice) ID
viewNoQuery string parameter — specifies which view (which attributes) of the resource is going to be present in the response.
project_idYesJSON request body field — unique identifier for the Procore project
commitment_idYesJSON request body field — unique identifier of the commitment
requisitionNoJSON request body field — requisition (Subcontractor Invoice)
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds permission-based constraints and partial update behavior, but lacks details on side effects, rate limits, or auth requirements beyond that.

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?

Description is well-structured and front-loaded with purpose, but includes API version and endpoint details that could be condensed; still reasonably concise.

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?

For a mutation tool with 5 well-documented parameters and no output schema, the description covers permission model, partial update behavior, and required parameters adequately.

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%, so the description adds only marginal value by listing required parameters and noting that requisition items are optional.

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 clearly states it updates a Requisition (Subcontractor Invoice), uses a specific verb and resource, and distinguishes easily from siblings like delete or show variants.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use based on user permissions and requisition status, but does not mention alternatives or 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