Skip to main content
Glama
TylerIlunga

Procore MCP Server

Restoring An Equipment (Deprecated)

restoring_an_equipment
Idempotent

Restore a project's equipment by providing its ID and optional field updates. Omitted fields remain unchanged, enabling reactivation of managed equipment records.

Instructions

Restoring 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 restoring an 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}/restore

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?

The description discloses substantial behavioral details: partial update semantics (omitted fields keep current values), payload nesting (fields sent at top level), defaulting of project_id, id resolution requirement, return value, and error status codes with common causes. Annotations provide idempotentHint and destructiveHint, but the description adds far more context about how the operation behaves, making it highly transparent.

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 long but packed with necessary information, including deprecation, usage semantics, parameter rules, return value, and error handling. It is well-structured, starting with the core action and deprecation. Minor redundancy exists ('Returns the modified restoring an equipment'), but no sentence is wastefully vague.

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?

Despite being a complex endpoint with deprecation, partial updates, and error handling, the description covers all essential aspects: what it does, deprecation timeline and alternative guidance, how to pass parameters, defaults, id resolution, return value, and error payloads. With no output schema, this level of detail is nearly exhaustive.

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 baseline is 3. The description adds meaning beyond the schema by explaining that only provided fields are updated, that the fields are passed at top level despite being nested in the payload, and that project_id defaults to config while id must reference an existing record. This helps the agent use the parameters correctly without needing to infer from the API shape.

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 it restores an equipment associated with a specified project, which is a specific action with clear scope. However, it does not differentiate from sibling restore tools like restore_equipment_company, and the name/description use the awkward gerund 'restoring' rather than a clear imperative. It is unambiguous in what it does, but sibling differentiation is weak.

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?

The description explicitly warns that the endpoint is deprecated and directs users to search for a newer version via procore_search_endpoints. It also provides usage guidance for partial updates, parameter defaults (project_id from config), and the need to resolve id first. It does not name a specific alternative tool, but the deprecation note is a strong when-not-to-use signal.

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