Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Commitment Change Order Batch

delete_commitment_change_order_batch
DestructiveIdempotent

Permanently delete a specified Commitment Change Order Batch using project ID and batch ID. This action cannot be undone.

Instructions

Delete the specified Commitment Change Order Batch. Use this to permanently delete the specified Commitments. This cannot be undone. Permanently removes the specified Commitments. This action cannot be undone. Required parameters: project_id, id. Procore API: Construction Financials > Commitments. Endpoint: DELETE /rest/v1.0/projects/{project_id}/commitment_change_order_batches/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — iD of the Commitment Change Order Batch
Behavior3/5

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

Annotations already declare destructiveHint=true. The description repeats 'cannot be undone' but adds no new behavioral context beyond 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 is somewhat repetitive, stating 'cannot be undone' twice and 'permanently deletes' similar ideas. Could be more concise.

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; description does not mention response or side effects. Slight ambiguity between 'Commitments' and 'Commitment Change Order Batch'. Adequate but not 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?

Schema coverage is 100%, so baseline is 3. Description only lists required parameters without adding meaning 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 it deletes the specified Commitment Change Order Batch and permanently removes Commitments. It distinguishes from siblings like create or update.

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 permanent deletion but does not explicitly state when to use vs alternative tools or provide exclusions. No alternatives mentioned.

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