Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Equipment Category (Company)

delete_equipment_category_company
DestructiveIdempotent

Permanently delete an equipment category from a company using the Procore API. Specify the category and company IDs to remove the record.

Instructions

Delete equipment category (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: category_id, company_id. Procore API (v2.0): Core > Equipment. Endpoint: DELETE /rest/v2.0/companies/{company_id}/equipment_register_categories/{category_id}

Input Schema

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

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

The description emphasizes the destructive nature ('permanently delete', 'cannot be undone') which aligns with the destructiveHint annotation. It adds context beyond annotations by explicitly stating the permanence and required parameters. No contradiction with annotations.

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, repeating 'cannot be undone' and 'permanently removes' twice. It is not concise; the same information could be conveyed in fewer words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and the description does not describe return values or behavior on success/failure. It includes API endpoint details which are helpful but repeats information. For a delete tool, more context on what the agent should expect after deletion would improve completeness.

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% with descriptions for both parameters. The description lists the required parameters but does not add additional meaning beyond what the schema already provides, earning the baseline score.

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 clearly states the verb (delete) and resource (equipment category at company level). The title and first sentence explicitly indicate 'Delete equipment category (Company)'. However, the description later refers to 'Equipment records' which is slightly inconsistent with deleting a category, causing minor confusion.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., delete_equipment_category_project, delete_equipment). The description does not mention when not to use it or provide alternative tool names.

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