Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_injuries

Retrieve injury records from Procore projects to manage workplace safety incidents. Filter by date, affected parties, body parts, or equipment for targeted reporting.

Instructions

List Injuries. [Project Management/Incidents] GET /rest/v1.0/projects/{project_id}/incidents/injuries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
incident_idNoIncident ID. When provided, the list will be scoped to only the Injuries for a given Incident.
pageNoPage
per_pageNoElements per page
filters__created_atNoReturn item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-...
filters__affected_company_idNoArray of Company IDs. Returns item(s) with the specified affected Company IDs.
filters__affected_party_idNoArray of Affected Party IDs. Returns item(s) with the specified Affected Party IDs.
filters__affected_person_idNoArray of Person IDs. Returns item(s) with the specified affected Person IDs.
filters__harm_source_idNoArray of Harm Source IDs. Returns item(s) with the specified Harm Source IDs.
filters__work_activity_idNoArray of Work Activity IDs. Returns item(s) with the specified Work Activity IDs.
filters__managed_equipment_idNoReturn item(s) with the specified Managed Equipment ID.
filters__recordableNoReturn item(s) that are recordable.
filters__affected_body_partNoReturn item(s) with any of the specified Affected Body Parts.
filters__affliction_type_idNoReturn item(s) with the specified Affliction Type IDs
filters__body_part_idNoReturn item(s) with the specified Body Part IDs
filters__filing_typeNoReturn item(s) with the specified filing types. The `recordable` filing_type filter value is deprecated.
filters__queryNoReturn item(s) containing query
sortNosort
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'List Injuries' and an API endpoint, failing to describe that this is a read-only list operation, that it supports pagination and filtering, or any rate limits or authentication requirements. This leaves critical behavioral traits unspecified for a tool with 18 parameters.

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 a single line with no wasted words, but it is under-specified rather than concise. It front-loads the tool name but lacks meaningful structure or elaboration. While not verbose, it fails to provide necessary information, making it inefficient in conveying value.

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 (18 parameters, no annotations, no output schema), the description is incomplete. It does not explain the tool's purpose beyond listing, omits behavioral context (e.g., read-only nature, pagination), and provides no output information. For a list tool with extensive filtering options, this leaves significant gaps in understanding.

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 fully documents all 18 parameters (e.g., project_id, filters, pagination). The description adds no parameter semantics beyond the schema, not even hinting at the filtering or pagination capabilities. With high schema coverage, the baseline is 3, but the description does not compensate with any additional context.

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 'List Injuries. [Project Management/Incidents] GET /rest/v1.0/projects/{project_id}/incidents/injuries' restates the tool name ('List Injuries') and adds only a category label and API endpoint. It lacks a specific verb+resource explanation (e.g., 'Retrieve a paginated list of injury records for a project') and does not distinguish it from sibling tools like 'list_incidents' or 'show_injury', making it vague beyond the name.

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 alternatives. It does not mention prerequisites (e.g., needing a project_id), exclusions, or comparisons to sibling tools like 'list_incidents' or 'show_injury'. The agent must infer usage from the parameters alone, which is insufficient for clear decision-making.

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