Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Compliance Document

create_compliance_document

Create a compliance document for a Procore Pay invoice by providing company, project, and invoice IDs. Document type, name, file IDs, and effective/expiration dates can be specified.

Instructions

Creates a compliance document Procore Pay must be enabled to use this endpoint.. Use this to create a new Payments in Procore. Creates a new Payments and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, invoice_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the Procore company
project_idYesURL path parameter — unique identifier for the Procore project
invoice_idYesURL path parameter — iD of the SC Invoice
nameNoJSON request body field — name of the compliance document
document_typeNoJSON request body field — document type of the compliance document
prostore_file_idsNoJSON request body field — array of Procore file IDs
effective_atNoJSON request body field — effective date of the compliance document
expires_atNoJSON request body field — expiration date of the compliance document
Behavior2/5

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

Annotations already indicate this is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it returns HTTP 201 and the created object, but does not disclose potential side effects, rate limits, or authentication details beyond the Procore Pay requirement. It provides minimal behavioral context beyond what annotations and the name imply.

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 relatively short but contains redundancy (e.g., 'Use this to create a new Payments in Procore. Creates a new Payments...'). Information is front-loaded but some phrases could be consolidated for clarity and brevity.

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?

Despite 100% schema coverage, the description lacks explanation of what a compliance document is and how it relates to payments. It does not clarify the return format or the meaning of all parameters. Given the complexity (8 parameters, no output schema), the description is insufficient for full understanding.

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 the baseline is 3. The description reiterates required parameters but does not add new semantic meaning beyond what the schema provides. It lists required parameters without additional context, and no non-required parameters are explained further.

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 description states it creates a compliance document, but mixes terms like 'new Payments in Procore', causing ambiguity. It identifies the resource and verb but does not clearly differentiate from similar sibling tools like 'create_a_compliance_document_project'. Overall purpose is somewhat muddled.

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 mentions a prerequisite (Procore Pay must be enabled) but provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., create_a_compliance_document_project), explicit differentiation is absent, and no 'when not to use' advice is 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