Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete An Equipment Model (Deprecated)

delete_an_equipment_model
DestructiveIdempotent

Permanently remove a specific equipment model from a company. Requires the model's ID and company ID; use the list or show tool to confirm the ID first.

Instructions

Detete a specific 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. Confirm the target id with the matching show or list tool before calling. 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. Permanently removes the equipment model. This cannot be undone, and a repeat call returns 404. 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. Procore API: Project Management > Field Productivity. Endpoint: DELETE /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
company_idYesURL path parameter — unique identifier for the company.
Behavior5/5

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

Beyond annotations, the description discloses permanent deletion, irreversibility, a repeat call returning 404, and specific error statuses (401/403/404). It also mentions the company_id config default. The idempotentHint is complemented, not contradicted, by the 404 note.

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 yet well-structured, front-loading purpose and deprecation. Every sentence adds value, but it is a bit long and contains a typo ('Detete'). It could be slightly tighter, but overall it earns a 4.

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 destructive, deprecated tool, the description covers all necessary context: deprecation timeline, prerequisites, side effects, error handling, config default, API category, and exact endpoint. Even with no output schema, it fully prepares the agent for invocation.

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

Parameters3/5

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

Schema coverage is 100%, but the schema description for 'id' appears inaccurate. The tool description partially compensates by stating that id must identify an existing parent record and should be resolved via list/show tools, but it does not explicitly clarify that id refers to the equipment model identifier.

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 clearly states the action and resource: 'Delete a specific equipment model' and later 'Permanently removes the equipment model.' This distinguishes it from sibling tools by naming the specific resource type.

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?

The description is explicit: it warns the endpoint is deprecated, tells the agent to prefer a newer version and use procore_search_endpoints, and instructs to confirm the target id with the matching show or list tool before calling. It also explains the id resolution prerequisite.

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