Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Equipment (Project)

update_equipment_project_company

Update existing equipment records in a Procore project. Specify project, company, and equipment IDs, then modify fields like name, serial number, or status.

Instructions

Update equipment (Project). 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: project_id, equipment_id, company_id. Procore API (v2.1): Core > Equipment. Endpoint: PATCH /rest/v2.1/companies/{company_id}/projects/{project_id}/equipment_register/{equipment_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — the Id of the project
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
onsiteNoJSON request body field — flag indicating to set or unset the equipment on the project.
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds value by clarifying it performs a partial update (PATCH), returns the modified object, and provides the HTTP method and API reference. This is more than what annotations convey, revealing partial update behavior and response structure.

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 three sentences: first states purpose, second details behavior, third lists required parameters and API info. It is front-loaded with the core action, uses no filler, and every sentence adds relevant information. Ideal length for quick comprehension.

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?

For a tool with 23 parameters and no output schema, the description covers the essential aspects: purpose, partial update behavior, required parameters, and API endpoint. It mentions return value (modified object). It does not discuss error handling or permissions, but given high schema coverage and clear annotations, it is sufficiently complete for practical 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 the schema already documents all parameters. The description adds meaning by explicitly listing required parameters (project_id, equipment_id, company_id), which goes beyond the schema's required array (only project_id and company_id). This clarifies that equipment_id is also mandatory for the operation, improving usability.

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 action (update), resource (Equipment records), and scope (Project-level). It specifies it's an update of existing records with partial updates (only supplied fields changed). The verb 'update' and resource 'equipment' are precise, and the title 'Update Equipment (Project)' helps distinguish from sibling tools for company-level or different versions.

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 provides basic guidance (use to update existing equipment, only supplied fields changed) but does not explicitly state when to use this tool versus alternatives like company-level updates or other versions (e.g., update_equipment_project_company_v2_0). It lacks exclusionary language or comparisons, leaving the agent to infer usage context from the name.

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