Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Equipment

update_equipment

Update existing equipment records in Procore Field Productivity by specifying company and equipment ID, modifying only the provided fields.

Instructions

Updating a piece of Equipment. 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: company_id, id. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/companies/{company_id}/managed_equipment/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
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
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that 'only the supplied fields are changed' (partial update) and 'returns the modified object on success', which provides context beyond annotations. However, it does not disclose potential side effects, validation behavior, or permission requirements.

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 concise, with three sentences that front-load the purpose, then add usage context and technical details. No unnecessary words or repetition.

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

Completeness3/5

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

Given the tool has 16 parameters and no output schema, the description adequately states the partial update behavior and return value. However, it omits details on error handling, validation, or common use cases, making it moderately complete.

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?

Input schema has 100% description coverage, so the schema already documents parameters. The description only highlights required parameters and mentions partial update, adding minimal semantic value beyond the schema.

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 states 'Updating a piece of Equipment' and 'update an existing Field Productivity records', clearly indicating the tool's purpose. It also specifies the API endpoint and required parameters, but does not explicitly differentiate from similar update_equipment sibling tools (e.g., v2.0 variants).

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

Usage Guidelines2/5

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

The description provides basic context ('Use this to update an existing...') and required parameters, but offers no guidance on when to use this tool versus alternatives like bulk_update_equipment or other versions. It lacks explicit when-to-use and when-not-to-use information.

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