Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A New Maintenance Record (Company)

create_a_new_maintenance_record_company

Create a new maintenance record for company equipment in Procore. Requires equipment ID, company ID, and type (planned/unplanned).

Instructions

Create a new maintenance record (Company). 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, company_id, equipment_id, type. Procore API (v2.0): Core > Equipment. Endpoint: POST /rest/v2.0/companies/{company_id}/equipment_register/{equipment_id}/maintenance/records

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
equipment_idYesJSON request body field — the id of the equipment.
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?

Description discloses creation behavior and HTTP 201 response. Annotations (readOnlyHint=false) are consistent. No additional behavioral context beyond creation.

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?

Four sentences, includes redundant mention of 'Equipment records' and duplicate 'equipment_id'. Front-loaded but could be more concise.

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?

Overview of creation and return value, plus API endpoint. Lacks description of optional parameters (issue, notes, etc.). Adequate but not comprehensive.

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?

Input schema covers all 7 parameters with descriptions (100% coverage). Description only repeats required parameters, adding no extra meaning.

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?

Description states the resource (maintenance record) and action (create) with company scope. It mentions 'Equipment records' but the resource is maintenance records, causing slight inconsistency. Still clear overall.

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 like create_equipment_maintenance_log or create_a_maintenance_record_project. No explicit when-not-to-use or alternative names 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