Skip to main content
Glama
TylerIlunga

Procore MCP Server

update_injury

Modify injury records in Procore projects to update incident details, treatment information, and safety documentation for compliance tracking.

Instructions

Update Injury. [Project Management/Incidents] PATCH /rest/v1.0/projects/{project_id}/incidents/injuries/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
idYesInjury ID
incident_idNoIncident ID
run_configurable_validationsNoWhether 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...
date_of_deathNoDate of death
descriptionNoDescription of event in Rich Text format
filing_typeNoFiling 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_overnightNoRepresents whether the injured person was hospitalized overnight
recordableNoRepresents whether the Injury record is recordable
treated_in_erNoRepresents whether the injured person was treated in the ER
treatment_facility_addressNoThe street address of the treatment facility
treatment_facilityNoThe name of the treatment facility
treatment_providerNoThe name of the treatment provider
work_days_absentNoThe number of days absent from work
work_days_restrictedNoThe number of days on restricted work
work_days_transferredNoThe number of days transferred
affliction_type_idNoThe ID of the Affliction Type. This cannot be cleared if there is an affected_body_part.
body_diagram_typeNobody_diagram_type
affected_body_partsNoDEPRECATED - Use body_part_ids instead. The body parts affected by the affliction. This requires an affliction_type to be set.
affected_person_idNoThe ID of the Affected Person. This only supports full Users from the Users endpoints.
affected_party_idNoThe ID of the Affected Person. This supports full and reference Users from the People endpoints.
body_part_idsNoThe IDs of body parts affected by the affliction. This requires an affliction_type to be set.
harm_source_idNoThe ID of the Harm Source
affected_company_idNoThe ID of the Affected Company
managed_equipment_idNoThe ID of the Managed Equipment
work_activity_idNoThe ID of the Work Activity
custom_field_%{custom_field_definition_id}NoValue 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?

No annotations are provided, so the description carries full burden. It states 'Update Injury' which implies a mutation, but fails to disclose behavioral traits such as required permissions, whether partial updates are allowed, validation rules (e.g., configurable validations), or side effects. The mention of PATCH in the description hints at partial updates but is not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is under-specified, not concise. It wastes space with redundant information like '[Project Management/Incidents] PATCH /rest/v1.0/projects/{project_id}/incidents/injuries/{id}' which is not helpful for an AI agent. It lacks front-loaded, actionable information.

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 complexity (27 parameters, no annotations, no output schema), the description is inadequate. It does not explain the tool's role in the incident management workflow, what constitutes a valid update, or the expected response format. For a mutation tool with many parameters, more context is needed.

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 the schema documents all 27 parameters thoroughly. The description adds no parameter semantics beyond what the schema provides, such as explaining relationships between fields (e.g., affliction_type_id and body_part_ids). Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update Injury' is a tautology that merely restates the tool name without adding clarity. It lacks a specific verb and resource context beyond what's implied by the name, and does not differentiate from sibling tools like 'update_incident' or 'update_environmental'.

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

Usage Guidelines1/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 alternatives. The description does not mention prerequisites, context (e.g., after creating an injury), or sibling tools like 'create_injury' or 'destroy_injury' for deletion.

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