Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Equipment (Company)

update_equipment_company_v2_1

Update specified fields of an existing equipment record in a company. Provide equipment ID and company ID; only supplied fields are changed.

Instructions

Update equipment (Company). Use this to update an existing Equipment records (only the supplied fields are changed). Updates the specified Equipment records and returns the modified object on success. Required parameters: equipment_id, company_id. Procore API (v2.1): Core > Equipment. Endpoint: PATCH /rest/v2.1/companies/{company_id}/equipment_register/{equipment_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
equipment_idNoJSON request body field — unique identifier of the equipment
company_idYesURL path parameter — unique identifier for the company.
equipment_nameNoJSON request body field — the equipment name for this Equipment operation
nameNoJSON request body field — the name of the equipment.
identification_numberNoJSON request body field — the identification number of the equipment.
serial_numberNoJSON request body field — the serial number of the equipment.
profile_photoNoJSON request body field — the profile photo for this Equipment operation
category_idNoJSON request body field — the category of the equipment.
type_idNoJSON request body field — the type of the equipment.
make_idNoJSON request body field — the make of the equipment.
model_idNoJSON request body field — the model of the equipment.
status_idNoJSON request body field — the status of the equipment.
yearNoJSON request body field — the year of the equipment.
rate_per_hourNoJSON request body field — the rate per hour for this Equipment operation
ownershipNoJSON request body field — the ownership for this Equipment operation
notesNoJSON request body field — the notes for this Equipment operation
assignee_idsNoJSON request body field — the people id of the equipment.
vendor_idNoJSON request body field — the vendor id of the equipment.
rental_start_dateNoJSON request body field — the start date of the rental.
rental_end_dateNoJSON request body field — the end date of the rental.
group_idsNoJSON request body field — list of group IDs to be associated with the equipment
Behavior4/5

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

The description adds value beyond annotations by clarifying that only supplied fields are changed (partial update) and that the modified object is returned on success. Annotations (readOnlyHint=false, destructiveHint=false) are consistent, and the description provides specific endpoint and version details.

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 relatively concise with four sentences covering purpose, behavior, required parameters, and endpoint. It could be slightly more streamlined by removing the first sentence which repeats the title, but overall it's clear and well-structured.

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 21 parameters with nested objects and no output schema, the description adequately explains the return object and partial update behavior but does not elaborate on nested parameter structures or error conditions. It is sufficient but not comprehensive.

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?

Schema coverage is 100% with descriptions for all parameters, so the bar is a baseline of 3. The description repeats some parameter info but adds no new meaning beyond the schema. The note about required parameters is partially inaccurate (only company_id is required per schema) but does not improve semantics.

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 tool updates existing equipment records, specifying that only supplied fields are changed and that it returns the modified object. It includes the API endpoint and version, distinguishing it from sibling tools like create or bulk update.

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

Usage Guidelines3/5

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

The description indicates to use this tool for updating existing equipment records and notes required parameters (equipment_id, company_id), but it does not explicitly mention when not to use it or provide alternatives like the bulk update variant.

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