Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A New Maintenance Record (Project)

create_a_new_maintenance_record_project

Create a new equipment maintenance record in a Procore project. Specify the equipment ID, project ID, company ID, and type (planned or unplanned) to log maintenance tasks.

Instructions

Create a new maintenance record (Project). Use this to create a new Equipment records in Procore. Creates a new Equipment records and returns the created object on success (HTTP 201). Required parameters: equipment_id, project_id, company_id, equipment_id, type. Procore API (v2.0): Core > Equipment. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/equipment_register/{equipment_id}/maintenance/records

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
equipment_idYesJSON request body field — the id of the equipment.
project_idYesURL path parameter — unique identifier for the project.
company_idYesURL path parameter — unique identifier for the company.
typeYesJSON request body field — the type of maintenance.
issueNoJSON request body field — description of the maintenance issue.
notesNoJSON request body field — notes about the maintenance.
start_dateNoJSON request body field — start date for equipment maintenance.
durationNoJSON request body field — duration in days.
Behavior3/5

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

The description adds behavioral context beyond annotations by indicating HTTP 201 and returning the created object. Annotations already signal a write operation (readOnlyHint=false). The description does not contradict annotations but also does not cover idempotency or side effects in detail.

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 concise with a front-loaded purpose statement. However, it contains a redundant sentence and an error (duplicate equipment_id), which detracts from effectiveness.

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?

The description is incomplete given the tool's complexity (8 parameters, no output schema). It lacks details on optional fields, default values, error handling, and explanation of the 'type' enum. The endpoint info is helpful but insufficient for full understanding.

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

Parameters2/5

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

The description repeats the required parameters but adds no additional meaning beyond the input schema, which already has 100% coverage. The duplication of 'equipment_id' introduces confusion rather than clarity.

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 the tool creates a 'maintenance record (Project)' and provides the endpoint and required parameters. It clearly identifies the operation but lacks explicit differentiation from the company-level sibling tool.

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 does not provide guidance on when to use this tool versus alternatives. It lacks explicit when-to-use/when-not-to-use information and does not mention any sibling tools or exclusions.

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