Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update An Equipment Model (Deprecated)

update_an_equipment_model
Idempotent

Update equipment model details in Procore by sending only the fields to change. Modify name, make, type, or active status for a given model.

Instructions

Update a specified equipment model. 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_model" 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 model 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: id, company_id, name, managed_equipment_make_id, managed_equipment_type_id. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/companies/{company_id}/managed_equipment_models/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the company to get the models for
nameYesJSON request body field — name of the equipment model
is_activeNoJSON request body field — if the equipment model is active
company_idYesURL path parameter — unique identifier for the company.
managed_equipment_make_idYesJSON request body field — equipment make ID the model is associated to
managed_equipment_type_idYesJSON request body field — equipment type ID the model is associated to
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses deprecation status, removal date, partial update behavior, payload nesting convenience, default company_id behavior, id validation, return value, and common error scenarios. This is rich behavioral context.

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 front-loaded with purpose and deprecation, and each sentence adds useful information. It is somewhat verbose and repeats the required parameters list already present in the schema, but the structured flow from purpose → deprecation → usage → errors is effective.

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?

The description covers purpose, deprecation, partial update behavior, parameter defaults, id resolution, return value, and error handling. With no output schema, this is fairly complete. However, the internal contradictions about required vs optional parameters and company_id defaulting create confusion, preventing a perfect score.

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

Parameters2/5

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

While the schema already covers all parameter descriptions (100% coverage), the description adds some helpful context about nesting and id resolution. However, it contradicts the schema by stating 'company_id defaults when omitted' and 'send only fields you intend to change' while the schema marks company_id, name, and other fields as required. This inconsistency undermines parameter clarity.

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 'Update a specified equipment model,' clearly identifying the verb and resource. It distinguishes this from sibling tools by specifying 'equipment model' rather than equipment, type, or make, and even includes the exact endpoint.

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 strong usage guidance including when NOT to use it (deprecated, prefer newer version via procore_search_endpoints) and prerequisites (resolve id with matching list tool first). Also explains partial update semantics, making it clear when this tool is appropriate.

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