Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update An Equipment

update_an_equipment

Update an existing equipment record in a Procore project. Modify fields such as name, serial number, status, or ownership to keep field productivity data current.

Instructions

Updating an equipment associated with the specified project. Use this to update an existing Field Productivity records (only the supplied fields are changed). Updates the specified Field Productivity records and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/projects/{project_id}/managed_equipment/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Field Productivity resource
current_project_idNoJSON request body field — iD of the project the equipment is currently dispatched to
nameNoJSON request body field — name of the equipment
serial_numberNoJSON request body field — serial number of the equipment
identification_numberNoJSON request body field — identification number of the equipment
descriptionNoJSON request body field — description of the equipment
managed_equipment_make_idNoJSON request body field — iD of the equipment make
managed_equipment_model_idNoJSON request body field — iD of the equipment model
managed_equipment_type_idNoJSON request body field — iD of the equipment type
managed_equipment_category_idNoJSON request body field — iD of the equipment category
company_visibleNoJSON request body field — the company visible for this Field Productivity operation
yearNoJSON request body field — year the equipment was manufactured in
statusNoJSON request body field — the status for this Field Productivity operation
ownershipNoJSON request body field — the type of ownership
upload_uuidsNoJSON request body field — array of upload uuids
Behavior4/5

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

Annotations already indicate non-destructive and non-idempotent behavior. The description adds that only supplied fields change and returns the modified object, providing helpful context beyond the structured annotations.

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?

Four sentences with some redundancy (first and third sentences repeat purpose). Still efficient but could be more 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?

Covers purpose, partial update, return value, and required parameters. Missing error conditions or prerequisites, but adequate for a single-update tool with good schema and annotation coverage.

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?

All 16 parameters have schema descriptions (100% coverage). The description does not add additional meaning beyond stating which are required, so baseline of 3 applies.

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 'Updating an equipment associated with the specified project' with a specific verb and resource. It distinguishes from bulk update siblings by focusing on a single record update.

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?

The description explains it's a partial update ('only the supplied fields are changed') and lists required parameters. However, it does not explicitly contrast with bulk_update_managed_equipment or mention 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