Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Equipment (Project)

create_equipment_project

Add new equipment records to a Procore project, specifying ownership, category, and type.

Instructions

Create equipment (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: project_id, company_id, name, identification_number, status_id, category_id, type_id, ownership. Procore API (v2.1): Core > Equipment. Endpoint: POST /rest/v2.1/companies/{company_id}/projects/{project_id}/equipment_register

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — the Id of the project
company_idYesURL path parameter — unique identifier for the company.
equipment_nameNoJSON request body field — the equipment name for this Equipment operation
nameYesJSON request body field — the name of the equipment.
equipment_idNoJSON request body field — unique identifier of the equipment
identification_numberYesJSON request body field — the identification number of the equipment.
status_idYesJSON request body field — the status of the equipment.
serial_numberNoJSON request body field — the serial number of the equipment.
profile_photoNoJSON request body field — the profile photo for this Equipment operation
category_idYesJSON request body field — the category of the equipment.
type_idYesJSON request body field — the type of the equipment.
make_idNoJSON request body field — the make of the equipment.
model_idNoJSON request body field — the model of the equipment.
yearNoJSON request body field — the year of the equipment.
rate_per_hourNoJSON request body field — the rate per hour of the equipment.
ownershipYesJSON request body field — the ownership of the equipment.
assignee_idsNoJSON request body field — the people id of the equipment.
vendor_idNoJSON request body field — the vendor id of the equipment.
rental_start_dateNoJSON request body field — the start date of the rental.
rental_end_dateNoJSON request body field — the end date of the rental.
notesNoJSON request body field — the notes for this Equipment operation
group_idsNoJSON request body field — list of group IDs to be associated with the equipment
onsiteNoJSON request body field — flag indicating to set or unset the equipment on the project.
Behavior3/5

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

Annotations already indicate non-read-only, non-destructive, non-idempotent behavior. The description adds that the tool returns the created object on success (HTTP 201). It does not mention potential side effects, error conditions, or authentication requirements beyond the endpoint.

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 (three sentences) and front-loads the core action. It could be improved with bullet points or clearer structure, but it is not verbose.

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?

Given the tool's complexity (23 parameters, many siblings, no output schema), the description lacks information about the created object's structure, error handling, and differentiation from similar tools. The required parameter list is helpful but incomplete.

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 each parameter is already well-described in the schema. The description only lists required parameters without adding any extra meaning or context beyond what the schema provides.

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 clearly specifies the action (create) and resource (Equipment records in Procore), and the title includes '(Project)' to indicate scope. However, it does not differentiate from sibling tools like 'create_equipment_company' or 'create_a_piece_of_equipment', leaving some ambiguity.

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 is provided on when to use this tool versus other equipment creation tools. The description lists required parameters but offers no context on typical use cases or prerequisites.

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