Skip to main content
Glama
TylerIlunga

Procore MCP Server

Updates A Transfer Document Header.

updates_a_transfer_document_header
Idempotent

Update transfer document header fields such as title, notes, and status to move documents through workflow states in Procore.

Instructions

Updates header fields such as title, notes, and status on the transfer document. Use status transitions to move the transfer through its workflow states. 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 id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified transfer document header 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: id, company_id, project_id. Procore API (v2.0): Resource Management > Materials Management. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/materials_mgmt/transfers/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — the transfer document ID.
nameNoJSON request body field — name of the document header.
notesNoJSON request body field — notes associated with the document header.
stateNoJSON request body field — the state for this Materials Management operation
company_idYesURL path parameter — the company identifier
project_idYesURL path parameter — the project identifier
descriptionNoJSON request body field — description of the document header.
properties_to_addNoJSON request body field — collection of resource parameters to add to the document header.
properties_to_deleteNoJSON request body field — collection of resource parameters to delete from the document header.
properties_to_updateNoJSON request body field — collection of resource parameters to update in the document header.
Behavior5/5

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

The description goes well beyond the annotations by explaining PATCH semantics ('omitted fields keep their current values'), defaulting behavior for company_id/project_id, the prerequisite of an existing parent record, success return value, and common error statuses (401, 403, 404). This gives the agent a clear picture of behavior and failure modes.

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?

The description is information-dense and every sentence earns its place, covering purpose, status transitions, defaults, errors, and the endpoint. However, it is a single paragraph with no visual structure, which slightly reduces readability. It is appropriately sized for the tool's complexity.

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?

With no output schema, the description compensates by stating the return value and error behavior. It covers prerequisites, required parameters, and endpoint. It could be improved by naming the specific 'matching list tool' and explicitly contrasting with line-item or attachment update tools, but overall it provides enough context for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for the required parameters: company_id and project_id default to procore_set_config values when omitted, and id must identify an existing parent record. It does not elaborate on properties_to_add/delete/update beyond their schema descriptions, but those are secondary.

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 states a specific verb and resource: 'Updates header fields such as title, notes, and status on the transfer document.' This clearly distinguishes it from sibling tools like 'updates_the_specified_transfer_line_item' and 'recycles_a_transfer_document' by scoping to header-level fields.

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?

It gives concrete when-to-use guidance: 'Use status transitions to move the transfer through its workflow states' and advises resolving the id via 'the matching list tool first.' It also explains partial-update behavior. However, it does not name the exact list tool or explicitly contrast with closely related update tools (e.g., line-item updates), so exclusions are only implicit.

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