Skip to main content
Glama
TylerIlunga

Procore MCP Server

Retrieve Equipment (Deprecated)

retrieve_equipment
Idempotent

Restore a previously deleted piece of equipment in Procore. Update its fields to bring it back into active use.

Instructions

Restore a piece of Equipment. 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. company_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: company_id, id. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/companies/{company_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
company_idYesURL path parameter — unique identifier for the company.
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?

Annotations are limited to readOnlyHint/idempotentHint/destructiveHint. The description adds essential behavioral details: PATCH semantics (send only changed fields, omitted fields retain values), company_id defaulting from procore_set_config, return value on success, and failure payloads with typical HTTP statuses. These go well beyond annotation hints.

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 dense and front-loaded with the main purpose. Each sentence contributes useful information (deprecation, payload mapping, error handling), though the deprecation explanation is slightly verbose and could be more concise without losing value.

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 complex tool with 16 parameters and no output schema, the description covers all necessary context: operation, deprecation, parameter usage, return value, and common failure modes. It fully compensates for the lack of an output schema and is complete for an agent to invoke correctly.

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?

Despite 100% schema coverage, the description adds crucial meaning: top-level arguments are nested under 'managed_equipment' in the payload, company_id has a default, and id must identify an existing record. It explains that fields are optional for partial updates, which is not evident from the schema alone.

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 starts with 'Restore a piece of Equipment', a specific verb+resource construction that clearly identifies the operation. It distinguishes this tool from siblings by noting the deprecation and directing users to newer versions via procore_search_endpoints.

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?

Explicitly states the endpoint is deprecated, advises using a newer version if available, and tells the agent to find it with procore_search_endpoints. It also instructs to resolve the id with the matching list tool first, offering clear when-to-use and prerequisite guidance.

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