Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A New Equipment

create_a_new_equipment

Add a new managed equipment item to a Procore project's field productivity records. Provide project ID and optional details like name, serial number, and status.

Instructions

Create a new equipment associated with the specified project. Use this to create a new Field Productivity records in Procore. Creates a new Field Productivity records and returns the created object on success (HTTP 201). Required parameters: project_id. Procore API: Project Management > Field Productivity. Endpoint: POST /rest/v1.0/projects/{project_id}/managed_equipment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
current_project_idNoJSON request body field — iD of the project the equipment is currently dispatched to
nameNoJSON request body field — name of the equipment
serial_numberNoJSON request body field — serial number of the equipment
identification_numberNoJSON request body field — identification number of the equipment
descriptionNoJSON request body field — description of the equipment
managed_equipment_make_idNoJSON request body field — iD of the equipment make
managed_equipment_model_idNoJSON request body field — iD of the equipment model
managed_equipment_type_idNoJSON request body field — iD of the equipment type
managed_equipment_category_idNoJSON request body field — iD of the equipment category
company_visibleNoJSON request body field — the company visible for this Field Productivity operation
yearNoJSON request body field — year the equipment was manufactured in
statusNoJSON request body field — the status for this Field Productivity operation
ownershipNoJSON request body field — the type of ownership
upload_uuidsNoJSON request body field — array of upload uuids
Behavior4/5

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description adds context by stating it returns the created object on success (HTTP 201) and provides the endpoint URL. This supplements the annotations effectively. No contradictions found.

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 four sentences long and contains the essential elements: purpose, usage context, success behavior, and required parameter. While it is reasonably concise, some repetition exists (e.g., 'Field Productivity records' mentioned twice). No superfluous information.

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 (15 parameters, no output schema), the description provides the endpoint and HTTP response code but does not explain how this tool differs from similar equipment creation tools or what 'Field Productivity' means. It also does not discuss potential side effects or prerequisites beyond project_id. Slightly incomplete for a complex API.

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?

The input schema has 100% coverage with descriptions for all 15 parameters. The description only reiterates that 'project_id' is required, adding no new semantic information beyond what the schema already provides. Baseline score of 3 is appropriate.

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 'Create a new equipment associated with the specified project' using a specific verb ('Create') and resource ('new equipment'). It also mentions the domain ('Field Productivity records') and provides the endpoint. However, it does not differentiate from sibling tools like 'create_equipment' or 'create_a_piece_of_equipment', which slightly reduces clarity.

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 mentions 'Use this to create a new Field Productivity records' and lists the required parameter, but it does not specify when to use this tool versus alternatives or provide exclusion criteria. Given the large number of sibling tools that create equipment (e.g., create_equipment, create_equipment_company), this lack of guidance limits its usefulness.

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