Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Compliance Document.

create_a_compliance_document_project

Create a compliance document on a contract to track bonds, licenses, permits, safety documents, or W9 forms. Set status and attach files to ensure contract compliance.

Instructions

Create a compliance document on a contract. Use this to create a new Commitments in Procore. Creates a new Commitments and returns the created object on success (HTTP 201). Required parameters: project_id, contract_id. Procore API: Construction Financials > Commitments. Endpoint: POST /rest/v1.0/projects/{project_id}/work_order_contracts/{contract_id}/compliance_documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
contract_idYesURL path parameter — identifier for the commitment contract
nameNoJSON request body field — the name for this Commitments operation
notesNoJSON request body field — the notes for this Commitments operation
typeNoJSON request body field — the type for this Commitments operation
statusNoJSON request body field — the status for this Commitments operation
effective_atNoJSON request body field — the effective at for this Commitments operation
expires_atNoJSON request body field — the expires at for this Commitments operation
send_expiration_notificationNoJSON request body field — send_expiration_notification
attachment_idsNoJSON request body field — existing attachments to preserve on the response
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
file_version_idsNoJSON request body field — file Versions to attach to the response
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
upload_idsNoJSON request body field — uploads to attach to the response
Behavior3/5

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

Annotations already indicate it is a write operation (readOnlyHint=false) and not destructive. The description adds that it returns HTTP 201 and the created object, which is useful. But it does not disclose idempotency or side effects.

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, but the first two sentences are slightly redundant. It front-loads the purpose and includes endpoint and HTTP status efficiently.

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?

Without an output schema, the description mentions it returns the created object but doesn't describe its structure. It covers core purpose and required params, but leaves details like parameter meanings to the schema.

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 description coverage is 100%, so parameter details are already in the schema. The description adds no new parameter meaning beyond listing required parameters (already in schema).

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 states it creates a compliance document on a contract, but confuses the object by calling it 'Commitments' in one sentence. It identifies the specific resource and distinguishes from siblings by requiring project_id and contract_id.

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?

No guidance on when to use this tool versus alternatives (e.g., create_compliance_document or v1_0 versions). It does not mention when not to use or prerequisites beyond required parameters.

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