Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Change Order Request

show_change_order_request
Read-onlyIdempotent

Retrieve full details of a specific change order request by its ID, project ID, and contract ID.

Instructions

Return detailed information about a specified Change Order Request (COR). Use this to fetch the full details of a specific Change Orders by its identifier. Returns a JSON object describing the requested Change Orders. Required parameters: id, project_id, contract_id. Procore API: Construction Financials > Change Orders. Endpoint: GET /rest/v1.0/change_order_requests/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Change Orders resource
project_idYesQuery string parameter — unique identifier for the project.
contract_idYesQuery string parameter — unique identifier of the contract
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 provide readOnlyHint=true, destructiveHint=false, etc. The description adds the Procore API endpoint and resource path, but does not disclose additional behavioral traits such as rate limits or authorization needs. It provides marginal value 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 concise with four sentences. It front-loads the purpose and is free of fluff. It could be slightly more concise, but it is well-structured for quick reading.

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?

Given no output schema, the description notes the return type (JSON object) but not detailed fields. Parameters are well-documented in the schema, and annotations cover safety. The tool is a straightforward show operation, and the description is adequately complete for an agent to use it correctly.

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 coverage is 100%, so baseline is 3. The description repeats the required parameters but adds no new meaning beyond what the schema already provides (e.g., path vs query parameter is in schema). No additional semantics.

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 verb 'Return detailed information' and the resource 'Change Order Request'. It specifies fetching by identifier, making the purpose distinct. However, it does not explicitly differentiate from sibling tools, which are numerous, but the action is well-defined.

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 indicates when to use the tool (to fetch full details) and lists required parameters. It does not provide explicit guidance on when not to use or mention alternative tools, but the context implies its usage for retrieving a specific COR.

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