Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Equipment Make (Company)

delete_equipment_make_company
DestructiveIdempotent

Permanently delete an equipment make record for a company by providing the make and company identifiers. This action cannot be undone.

Instructions

Delete equipment make (Company). Use this to permanently delete the specified Equipment records. This cannot be undone. Permanently removes the specified Equipment records. This action cannot be undone. Required parameters: make_id, company_id. Procore API (v2.0): Core > Equipment. Endpoint: DELETE /rest/v2.0/companies/{company_id}/equipment_register_makes/{make_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
make_idYesURL path parameter — unique identifier of the make
company_idYesURL path parameter — unique identifier for the company.
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds emphasis on irreversibility ('cannot be undone') and mentions required parameters, adding context beyond annotations. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains redundancy ('permanently delete' appears twice, 'cannot be undone' appears twice). It is clear but could be more concise.

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?

For a simple delete operation with full schema coverage and annotations, the description provides adequate context including irreversibility, required parameters, and API endpoint. It is nearly complete.

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?

The input schema covers both parameters with 100% description coverage. The description only restates the parameter names and endpoint pattern, adding no new semantic meaning.

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 it is for deleting an equipment make (company). It specifies the action is permanent and distinguishes from sibling create and update tools.

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

Usage Guidelines3/5

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

The description implies usage for deletion but does not explicitly state when not to use or mention alternatives like update. It is adequate but lacks contrast.

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