Skip to main content
Glama
TylerIlunga

Procore MCP Server

Updates A Material Requirements Document Header.

updates_a_material_requirements_document_header
Idempotent

Update header details on a material requirements document, such as title, notes, and status, to move it through workflow states. Send only changed fields.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — the material requirements document ID.
nameNoJSON request body field — name of the document header.
notesNoJSON request body field — notes associated with the document header.
statusNoJSON request body field — the status 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.
scope_end_atNoJSON request body field — end date and time for the scope. Clears header field if value is an empty string or "0001-01-01T00:00:00.0000000+00:00".
scope_start_atNoJSON request body field — start date and time for scope. Clears header field if value is an empty string or "0001-01-01T00:00:00.0000000+00:00".
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.
required_on_site_dateNoJSON request body field — date and time by which the item is required to be on site.
Behavior5/5

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

Goes well beyond annotations: explains patch semantics (omitted fields keep values), config defaults, id resolution requirement, return value, and common HTTP error codes (401/403/404). No contradiction with annotations; idempotentHint is consistent with partial updates.

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?

Dense but efficient single paragraph; every sentence carries useful information (fields, behavior, defaults, errors, endpoint). Slightly long and could benefit from bullet points, but no wasted words.

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

Completeness5/5

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

For a 13-param tool with no output schema, the description covers purpose, use cases, patch behavior, config defaults, id prerequisite, return value, error handling, and API endpoint. Schema handles the remaining parameter details, making this highly complete.

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 value by explaining defaulting behavior for company_id/project_id, id resolution, and status transitions—context not evident from schema. This elevates it above baseline.

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 identifies the action ('Updates header fields such as title, notes, and status') on a specific resource ('material requirements document'), with concrete examples. It differentiates from line-item or full-document tools by explicitly scoping to header fields, though it doesn't name alternative tools.

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 clear context: status transitions for workflow states, partial-update semantics, config defaults for company_id/project_id, and a prerequisite to resolve id via a list tool. Does not explicitly name sibling alternatives for when-not-to-use, but the context is sufficient for correct invocation.

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