Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update An Equipment (Deprecated)

update_an_equipment
Idempotent

Update equipment details in a Procore project by providing the project ID and equipment ID. Only the fields you specify are changed, and the modified equipment record is returned.

Instructions

Updating an equipment associated with the specified project. DEPRECATED: Procore has deprecated this endpoint (as of 2024-12-01). It is scheduled for removal on 2025-12-02; prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "managed_equipment" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and 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: 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
idYesURL path parameter — unique identifier of the Field Productivity resource
nameNoJSON request body field — name of the equipment
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
project_idYesURL path parameter — unique identifier for the project.
descriptionNoJSON request body field — description of the equipment
upload_uuidsNoJSON request body field — array of upload uuids
serial_numberNoJSON request body field — serial number of the equipment
company_visibleNoJSON request body field — the company visible for this Field Productivity operation
current_project_idNoJSON request body field — iD of the project the equipment is currently dispatched to
identification_numberNoJSON request body field — identification number of the equipment
managed_equipment_make_idNoJSON request body field — iD of the equipment make
managed_equipment_type_idNoJSON request body field — iD of the equipment type
managed_equipment_model_idNoJSON request body field — iD of the equipment model
managed_equipment_category_idNoJSON request body field — iD of the equipment category
Behavior5/5

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

Goes well beyond annotations by disclosing PATCH semantics (only changed fields), payload nesting under managed_equipment, project_id defaulting to procore_set_config, and common error status codes (401, 403, 404). No contradiction with annotations; it enriches the behavioral profile.

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 long but tightly packed with essential information: deprecation details, partial update instructions, nesting, defaults, error codes, required parameters, and endpoint. Every sentence contributes value; nothing is redundant or filler.

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

Completeness5/5

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

For a 16-parameter tool with no output schema, this description fully covers usage, return value ('Returns the modified equipment'), failure modes, parameter behavior, and prerequisites. It is complete enough for an agent to invoke correctly without external lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already describes every parameter, the description adds critical semantics: top-level arguments are automatically nested in the payload, project_id defaults when omitted, and id must reference an existing parent record. This provides meaning the schema alone lacks.

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 opens with 'Updating an equipment associated with the specified project,' clearly identifying the verb and resource. It further distinguishes itself through an explicit deprecation notice and instruction to prefer a newer version, differentiating it from current alternatives like update_equipment.

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

Usage Guidelines5/5

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

Provides explicit guidance: the tool is deprecated, prefer a newer version, and use procore_search_endpoints to locate it. It also advises resolving the id with the matching list tool first and explains the partial update behavior, giving clear when-to-use and when-not-to-use context.

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