Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Equipment (Company)

create_equipment_company

Create new equipment records in Procore by providing required details like name, identification number, status, category, type, and ownership. Returns the created object.

Instructions

Create equipment (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: 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}/equipment_register

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
Behavior3/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description adds that the tool returns the created object on HTTP 201. However, it does not disclose side effects, authentication needs, or rate limits. The added context is moderate.

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 short and front-loaded with purpose. It includes necessary information in three sentences, though there is slight redundancy between the first two sentences. Overall, it is efficient.

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?

Given the complexity (21 parameters, no output schema) and the presence of sibling tools, the description provides the endpoint and required parameters but lacks details on return structure, error handling, and when to use company vs project versions. It is 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?

Schema coverage is 100%, so the baseline is 3. The description lists required parameters but does not add meaning beyond what the schema already provides (e.g., descriptions of each parameter are in the schema). No additional semantics are introduced.

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 states the tool creates equipment records, specifying the endpoint and required parameters. However, it does not explicitly differentiate from sibling tools like create_equipment_project, which would improve clarity.

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

Usage Guidelines3/5

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

The description indicates when to use the tool (to create equipment) but provides no guidance on when to use alternatives or when not to use it. Required parameters are listed, but no exclusions or context for decision-making are 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