Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Injury

create_injury

Add an injury record to an existing incident in Procore. Specify project, incident, and injury details to log workplace injuries.

Instructions

Creates an Injury record. NOTE: The afflictions and affected_body_part keys are deprecated. Please disregard and use the affected_body_parts and affliction_type keys as documented below. Use this to create a new Incidents in Procore. Creates a new Incidents and returns the created object on success (HTTP 201). Required parameters: project_id, incident_id. Procore API: Project Management > Incidents. Endpoint: POST /rest/v1.0/projects/{project_id}/incidents/injuries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
run_configurable_validationsNoQuery string parameter — whether or not Configurable validations from the Injury Configurable Field Set should be run (default: false). See (https://developers.procore.com/reference/configurable-field-sets#list-project-con...
incident_idYesJSON request body field — the ID of the Incident
date_of_deathNoJSON request body field — the date of death for this Incidents operation
descriptionNoJSON request body field — description of event in Rich Text format
date_returned_to_workNoJSON request body field — date returned to work
filing_typeNoJSON request body field — filing Type - The 'recordable' filing_type value is deprecated. When a filing type of 'recordable' is provided, the `recordable` attribute of the Injury will instead be set to 'true'.
hospitalized_overnightNoJSON request body field — represents whether the injured person was hospitalized overnight
recordableNoJSON request body field — represents whether the Injury record is recordable
treated_in_erNoJSON request body field — represents whether the injured person was treated in the ER
treatment_facility_addressNoJSON request body field — the street address of the treatment facility
treatment_facilityNoJSON request body field — the name of the treatment facility
treatment_providerNoJSON request body field — the name of the treatment provider
work_days_absentNoJSON request body field — the number of days absent from work
work_days_restrictedNoJSON request body field — the number of days on restricted work
work_days_transferredNoJSON request body field — the number of days transferred
affliction_type_idNoJSON request body field — the ID of the Affliction Type. This cannot be cleared if there is an affected_body_part.
body_diagram_typeNoJSON request body field — the body diagram type for this Incidents operation
affected_body_partsNoJSON request body field — dEPRECATED - Use body_part_ids instead. The body parts affected by the affliction. This requires an affliction_type to be set.
affected_person_idNoJSON request body field — the ID of the Affected Person. This only supports full Users from the Users endpoints.
affected_party_idNoJSON request body field — the ID of the Affected Person. This supports full and reference Users from the People endpoints.
body_part_idsNoJSON request body field — the IDs of body parts affected by the affliction. This requires an affliction_type to be set.
harm_source_idNoJSON request body field — the ID of the Harm Source
affected_company_idNoJSON request body field — the ID of the Affected Company
managed_equipment_idNoJSON request body field — the ID of the Managed Equipment
work_activity_idNoJSON request body field — the ID of the Work Activity
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior2/5

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

The description does not discuss side effects, permissions, or constraints beyond what annotations already convey. It mentions the HTTP 201 response but lacks detail on failure modes or data consistency.

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 somewhat redundant with repeated phrases ('Creates a new Incidents') and could be more concise. It front-loads the purpose effectively, but includes unnecessary repetition.

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?

For a creation tool with 27 parameters and no output schema, the description provides the endpoint and deprecation notes but lacks details on response structure, error handling, or guidance for complex parameter interactions.

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 baseline is 3. The description adds a note about deprecated keys but does not provide additional meaning for most parameters.

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 that the tool creates an Injury record and provides the HTTP method and endpoint. It distinguishes from siblings like create_incident by requiring incident_id. However, it redundantly says 'Creates a new Incidents' which is confusing.

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 explicit guidance on when to use this tool vs alternatives (e.g., update_injury). It only mentions required parameters but does not provide context on when to create vs update.

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