Skip to main content
Glama
TylerIlunga

Procore MCP Server

Updates An Adjustment Document Header.

updates_an_adjustment_document_header
Idempotent

Update adjustment document headers like title, notes, and status. Send only changed fields; omitted fields stay unchanged, and status transitions move the document through its workflow.

Instructions

Updates header fields such as title, notes, and status on the adjustment document. Use status transitions to move the adjustment 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 adjustment 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/adjustments/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — the adjustment 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.
Behavior4/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds valuable context: partial update semantics (omitted fields keep values), defaulting of company_id/project_id from procore_set_config, requirement that id must reference an existing parent record, and error handling details (401/403/404). It discloses the return value (modified header) and failure modes, which goes beyond annotations.

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 well-structured and front-loaded, starting with the core purpose and then providing additional context in a logical flow. Each sentence adds value: partial update semantics, defaults, id resolution, return value, error handling, and API reference. No redundant or filler content.

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 tool's complexity (10 parameters, mutation, error-prone), the description covers essential aspects: what it does, how to use it, error scenarios, and API endpoint. The lack of output schema is partially compensated by stating it returns the modified header. However, it does not explain the 'properties_to_add/delete/update' parameters in detail, which are complex and potentially confusing. Still, the description is quite complete for agent use.

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 baseline is 3. The description adds meaning beyond the schema by explaining partial update behavior (only send fields to change), defaulting of company_id/project_id when omitted, and the requirement to resolve id via a list tool. It also clarifies the 'state' parameter's role in status transitions. This enriches the raw schema descriptions.

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 the verb ('Updates') and the resource ('adjustment document header'), and specifies the fields involved (title, notes, status). It also distinguishes from siblings by focusing on header updates (e.g., 'updates_a_line_item_on_an_adjustment_document' handles line items). The scope is explicit and unambiguous.

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?

Provides explicit when-to-use guidance: 'Use status transitions to move the adjustment through its workflow states.' It also gives important usage constraints: 'Send only the fields you intend to change; omitted fields keep their current values,' and explains default behavior for company_id and project_id. It also instructs to resolve id with the matching list tool first, making the usage context clear.

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