Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show All Prime Change Orders

show_all_prime_change_orders
Read-onlyIdempotent

Retrieve all prime change orders for a specific project, with filters for status, contract, vendor, and pagination controls.

Instructions

Returns all Prime Change Orders for the specified Project. This endpoint currently only supports projects using 1 and 2 tier change order configurations. Use this to fetch the full details of a specific Prime Contracts by its identifier. Returns a paginated JSON array of Prime Contracts. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Construction Financials > Prime Contracts. Endpoint: GET /rest/v1.0/projects/{project_id}/prime_change_orders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
viewNoQuery string parameter — specifies Which view (which attributes) of the resource is going to be present in the response. the extended view includes change events data, while the default view does not.
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 ID
filters__batch_idNoQuery string parameter — filter results by Change Order Batch ID
filters__legacy_package_idNoQuery string parameter — filter results by legacy Change Order Package ID
filters__contract_idNoQuery string parameter — filter results by Contract ID
filters__vendor_idNoQuery string parameter — filter results by Contract Vendor ID
filters__signature_requiredNoQuery string parameter — filter results by signature_required
filters__executedNoQuery string parameter — filter results by executed
filters__statusNoQuery string parameter — filter results by status
filters__updated_atNoQuery string parameter — return item(s) within a specific updated at iso8601 datetime range
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already declare this as a read-only, non-destructive, idempotent operation. The description adds value by noting pagination behavior, required project_id, and configuration limitations (1/2 tier). 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 is moderately concise but includes redundant technical details (API route, endpoint) and the contradictory sentence. It could be streamlined.

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?

Without an output schema, the description adequately explains the return type (paginated JSON array) and pagination metadata. It covers the required parameter and configuration constraint. Lacks explanation of what a Prime Change Order is, but that is minor.

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. The description adds context about pagination control and metadata but does not further elaborate on individual parameters beyond what the schema already provides.

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 it returns all Prime Change Orders for a project and specifies support for 1 and 2 tier configurations. However, it contains a minor inconsistency by mentioning fetching a specific Prime Contract by identifier, which contradicts the 'all' nature.

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 provides contradictory guidance: first says returns all, then says use to fetch a specific. It mentions pagination but does not explicitly differentiate from sibling tools like show_prime_change_order. No when-not-to-use or alternatives given.

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