Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Payment Applications (Owner Invoices) For Prime Contract

list_payment_applications_owner_invoices_for_prime_contract
Read-onlyIdempotent

Retrieve a paginated list of owner invoices (payment applications) for a specific prime contract, with filtering and pagination support.

Instructions

Return a list of all Payment Applications (Owner Invoices) on a specified Prime Contract See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate Prime Contracts when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Prime Contracts. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: prime_contract_id, project_id. Procore API: Construction Financials > Prime Contracts. Endpoint: GET /rest/v1.0/prime_contracts/{prime_contract_id}/payment_applications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prime_contract_idYesURL path parameter — unique identifier of the prime contract
project_idYesQuery string parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — elements per page (default 30)
filters__is_lastNoQuery string parameter — setting this to true will return only the last item. Setting this to false will return all the items except the last one.
Behavior2/5

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

The description claims 'Returns a paginated JSON array of Prime Contracts,' but the tool actually returns Payment Applications. This is a behavioral contradiction that misrepresents the output. Annotations are consistent with a read-only operation, but the description adds misleading information.

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 mostly concise but includes a contradictory sentence about returning Prime Contracts, which wastes space and confuses the reader. The core information is front-loaded, but the error reduces clarity.

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?

Given the complexity (6 parameters, pagination, filters, no output schema), the description lacks completeness due to the internal inconsistency about return type. It fails to clarify the exact structure of the response, leaving an agent potentially misinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema by explicitly stating required parameters and explaining pagination usage with page and per_page. It also references filtering capabilities. Schema coverage is 100%, so the description complements it well.

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 explicitly states 'Return a list of all Payment Applications (Owner Invoices) on a specified Prime Contract' and provides additional context on use cases, making the primary purpose very clear.

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 contains a contradictory statement: 'Use this to enumerate Prime Contracts...' which misidentifies the resource being listed (it lists Payment Applications, not Prime Contracts). This is misleading and detracts from proper guidance on when to use the tool.

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