Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Equipment (Company)

update_equipment_company_v2_1
Idempotent

Update existing company equipment in Procore by sending only changed fields; omitted fields stay unchanged, requiring equipment_id and company_id.

Instructions

Updates an existing equipment for the specified Procore company. Send only the fields you intend to change; omitted fields keep their current values. company_id defaults to the value set by procore_set_config when omitted, and equipment_id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified equipment 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: equipment_id, company_id. Procore API (v2.1): Resource Management > Equipment. Endpoint: PATCH /rest/v2.1/companies/{company_id}/equipment_register/{equipment_id}

Input Schema

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

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

Beyond annotations (readOnly=false, destructive=false), the description discloses PATCH partial-update behavior, company_id fallback, the return value, and common error statuses (401/403/404). This gives the agent a concrete model of the tool's behavior. No contradiction with 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?

The description packs action, partial update, config default, prerequisite, return value, error handling, required params, and endpoint into a dense but well-organized paragraph. Every sentence earns its place, though it is near the upper bound of length.

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?

Given 22 parameters, no output schema, and annotations, the description covers the essential usage guidance and response/error behavior. The only notable gap is not naming the specific list tool for resolving equipment_id, but the instruction to resolve it first is present.

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 descriptions cover all 22 parameters generically (e.g., 'the name of the equipment'). The description adds semantic context: omitted fields keep current values, company_id has a config default, and equipment_id must reference an existing record—valuable meaning beyond the schema's per-field labels.

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 'Updates an existing equipment for the specified Procore company,' which is a clear verb+resource+scope. It does not explicitly distinguish from versioned/project-scoped siblings like update_equipment_company_v2_0 or update_equipment_project_company_v2_1, though the title and API version hint help.

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 explicit usage guidance: partial update semantics ('Send only the fields you intend to change; omitted fields keep their current values'), company_id default via procore_set_config, and the prerequisite to resolve equipment_id with the matching list tool. It does not name a specific alternative tool for when not to use this one, but the context is clear.

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