Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Prime Change Order

show_prime_change_order
Read-onlyIdempotent

Retrieve full details of a prime change order by project ID and change order ID. Use this endpoint to access change order information, with optional extended view for change events.

Instructions

Show the details of the Prime Change Order. 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 JSON object describing the requested Prime Contracts. Required parameters: project_id, id. Procore API: Construction Financials > Prime Contracts. Endpoint: GET /rest/v1.0/projects/{project_id}/prime_change_orders/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — iD of the Prime Change Order
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.
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 indicate read-only, idempotent, and non-destructive behavior. The description adds the important constraint of only supporting 1 and 2 tier configurations, and specifies the HTTP method (GET) and endpoint path. This provides useful 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.

Conciseness4/5

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

The description is relatively concise with a few sentences, front-loading the purpose. It includes some repetitive information (required parameters) but avoids unnecessary fluff.

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?

Given no output schema, the description vaguely states 'Returns a JSON object describing the requested Prime Contracts.' It does not mention the optional view parameter's impact on response structure or pagination parameters. The constraint about configuration tiers is helpful, but overall completeness is adequate but not thorough.

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?

The input schema already describes all 5 parameters with 100% coverage. The description redundantly lists required parameters and the endpoint path, adding little new meaning. The view parameter's effect on response is mentioned in schema but not highlighted in description.

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 tool shows details of a Prime Change Order, specifying it fetches full details by identifier. However, it does not differentiate this tool from siblings like show_prime_change_order_batch or show_all_prime_change_orders, which also fetch prime change order data.

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 fetching specific Prime Change Order details and notes the supported configuration tiers, but provides no explicit when-not-to-use guidance or alternatives. Sibling tools exist for listing or batch retrieval, but these are not 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