Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Compliance Document.

create_a_compliance_document_project

Create a compliance document for an existing commitment contract. Supply project and contract IDs, set fields like type, status, and notes, and receive the new document with its ID.

Instructions

Create a compliance document on a contract. Pass the record's fields as top-level arguments — they are nested under "attributes" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and contract_id must identify an existing parent record — resolve it with the matching list tool first. Creates the compliance document and returns it with its new id (HTTP 201); calling it again creates another record. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. 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
nameNoJSON request body field — the name for this Commitments operation
typeNoJSON request body field — the type for this Commitments operation
notesNoJSON request body field — the notes for this Commitments operation
statusNoJSON request body field — the status for this Commitments operation
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
expires_atNoJSON request body field — the expires at for this Commitments operation
project_idYesURL path parameter — unique identifier for the project.
upload_idsNoJSON request body field — uploads to attach to the response
contract_idYesURL path parameter — identifier for the commitment contract
effective_atNoJSON request body field — the effective at for this Commitments operation
attachment_idsNoJSON request body field — existing attachments to preserve on the response
file_version_idsNoJSON request body field — file Versions to attach to the response
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
send_expiration_notificationNoJSON request body field — send_expiration_notification
Behavior5/5

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

Goes well beyond the annotations by disclosing non-idempotency ('calling it again creates another record'), the 201 response with the new id, and common error statuses (401, 403, 404) with meaning. It also explains that fields are nested under 'attributes' in the payload, adding real transparency about request transformation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Every sentence delivers distinct value: purpose, payload handling, defaults, idempotency behavior, error handling, required parameters, API context, and endpoint. The structure is logical and front-loaded with the main purpose; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with 15 schema-documented parameters, the description covers all critical aspects: return value (new id, 201), non-idempotency, error scenarios with status codes, required parameter resolution, and API endpoint. The absence of an output schema is compensated by explicitly stating the response includes the new id. This is a complete, self-sufficient description.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that project_id defaults from configuration when omitted, contract_id must reference an existing parent record, and that record fields should be passed as top-level arguments. It does not describe the optional fields in detail, but the schema already covers those.

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 opens with a specific verb and resource: 'Create a compliance document on a contract.' It clearly identifies the operation (POST to a work_order_contracts endpoint) and the context (Construction Financials > Commitments), distinguishing it from sibling tools that operate on other contract types or compliance document listings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides actionable guidance: contract_id must identify an existing parent record and should be resolved with the matching list tool first, and project_id defaults from procore_set_config when omitted. It could be stronger by explicitly naming alternatives or stating when not to use this tool, but the context is clear and helpful.

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