Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show All Commitment Change Order Batches

show_all_commitment_change_order_batches
Read-onlyIdempotent

Retrieve all commitment change order batches for a project with filtering by ID, status, or date range. Supports pagination to manage large result sets.

Instructions

Returns all Commitment Change Order Batches for the specified Project. Use this to fetch the full details of a specific Commitments by its identifier. Returns a paginated JSON array of Commitments. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Construction Financials > Commitments. Endpoint: GET /rest/v1.0/projects/{project_id}/commitment_change_order_batches

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
filters__idNoQuery string parameter — filter results by Change Order Batch ID
filters__change_order_idNoQuery string parameter — filter results by Change Order ID
filters__contract_idNoQuery string parameter — filter results by Contract ID
filters__updated_atNoQuery string parameter — return item(s) within a specific updated at iso8601 datetime range
filters__statusNoQuery string parameter — array of Status. Return item(s) with the specified status.
filters__status__notNoQuery string parameter — array of Status. Return item(s) that does not have specified status.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, indicating a safe read operation. The description adds that the response is a paginated JSON array with pagination metadata, and specifies the endpoint. This is moderate additional context, but does not cover rate limits or other behavioral constraints.

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 fairly concise with two sentences, but the second sentence is somewhat redundant and introduces confusion (mixing 'Commitments' with 'batches'). It could be streamlined and made more precise.

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

Completeness2/5

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

With no output schema, the description should detail the response structure. It mentions a paginated JSON array but refers to 'Commitments' instead of 'Commitment Change Order Batches', which is misleading. It also does not explain how filters work or the response fields, leaving gaps for a 10-parameter tool.

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 description coverage is 100%, so all parameters are already described in the input schema. The description does not add new semantic meaning beyond mentioning project_id as required and page/per_page for pagination, which is already stated in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and first sentence clearly state the tool returns all Commitment Change Order Batches for a project. However, the second sentence mentions 'fetch the full details of a specific Commitments' which is inconsistent and confusing, as the tool returns batches, not commitments. This reduces clarity.

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?

The description does not provide guidance on when to use this tool versus alternatives like show_all_commitment_change_orders or show_all_prime_change_order_batches. There is no when-not-to-use or exclusion context, leaving the agent to infer usage from the name alone.

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