Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete Contributing Condition

delete_contributing_condition
DestructiveIdempotent

Permanently delete a custom Contributing Condition from Procore using company ID and condition ID. Note: Procore-provided conditions cannot be removed.

Instructions

Deletes a Contributing Condition. Note that Procore provided Contributing Conditions cannot be deleted. Use this to permanently delete the specified Incidents. This cannot be undone. Permanently removes the specified Incidents. This action cannot be undone. Required parameters: company_id, id. Procore API: Project Management > Incidents. Endpoint: DELETE /rest/v1.0/companies/{company_id}/contributing_conditions/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — contributing Condition ID

Tool Definition Quality

A3.7/5.0
Behavior4/5

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

Beyond annotations (destructiveHint=true), the description adds that the action is permanent and cannot be undone, and notes a restriction on Procore provided conditions. This is useful context not fully captured by annotations.

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

Conciseness2/5

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

The description is verbose with redundant phrases (e.g., 'This cannot be undone' appears twice) and includes unnecessary API endpoint details. It 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 tool with no output schema, the description covers the core action, permanence, and a key constraint (Procore provided conditions), providing adequate context.

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?

Input schema has 100% coverage with descriptions for both parameters. The description only repeats that company_id and id are required, adding no new semantics beyond the schema.

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 tool deletes a Contributing Condition and explicitly notes that Procore provided ones cannot be deleted, which distinguishes it from sibling tools like delete_contributing_behavior.

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 (permanently delete) but does not provide explicit guidance on when to use vs. alternatives or when not to use it.

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