Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_incident_alerts

Retrieve incident alerts for a Procore project to monitor safety notifications and manage construction site incidents.

Instructions

List Incident Alerts. [Project Management/Incidents] GET /rest/v1.0/projects/{project_id}/incidents/alerts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
incident_idNoIncident ID
pageNoPage
per_pageNoElements per page
filters__idNoReturn item(s) with the specified IDs.
filters__updated_atNoReturn item(s) last updated 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 `YYY...
filters__incident_idNoReturn item(s) with the specified Incident IDs.
filters__injury_idNoReturn item(s) with the specified Injury IDs.
filters__recipient_idNoReturn item(s) with the specified recipient (User) IDs
filters__severity_level_idNoReturn item(s) with the specified Incident Severity Level IDs
filters__triggered_by_idNoReturn item(s) with the specified triggered by (User) IDs
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. It mentions 'GET' which implies a read-only operation, but does not disclose behavioral traits such as pagination behavior, rate limits, authentication needs, or what the response looks like. The description is minimal and lacks essential operational details.

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

Conciseness5/5

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

The description is extremely concise with just one sentence, front-loaded with the core purpose. There is no wasted verbiage, making it efficient and easy to parse, though it may be too brief for completeness.

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 of 12 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain the return format, pagination, filtering logic, or any behavioral context needed for effective use, leaving significant gaps for the agent.

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 already documents all 12 parameters thoroughly. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('List') and resource ('Incident Alerts'), which is specific and understandable. It does not distinguish from sibling tools, as there are many list operations but none specifically for incident alerts, so it's adequately clear but not differentiated.

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 provides no guidance on when to use this tool versus alternatives. It includes a category tag '[Project Management/Incidents]' and an API endpoint, but these do not offer usage context, prerequisites, or comparisons with other tools.

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