Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Accident Logs

list_accident_logs
Read-onlyIdempotent

Retrieve accident logs for a Procore project. Filter by date range or paginate results to review incident records.

Instructions

Returns all Accident Logs for the current date. See Working with Daily Logs for information on filtering the response using the log_date, start_date, and end_date parameters. Note that if none of the date parameters are provided in the call, only logs from the current date are returned. Use this to enumerate Daily Log records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Daily Log records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Daily Log. Endpoint: GET /rest/v1.0/projects/{project_id}/accident_logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
pageNoQuery string parameter — page number for paginated results (default: 1)
log_dateNoQuery string parameter — date of specific logs desired in YYYY-MM-DD format
start_dateNoQuery string parameter — start date of specific logs desired in YYYY-MM-DD format (use together with end_date)
end_dateNoQuery string parameter — end date of specific logs desired in YYYY-MM-DD format (use together with start_date)
filters__created_by_idNoQuery string parameter — return item(s) created by the specified User ID
filters__location_idNoQuery string parameter — return item(s) with the specified Location IDs.
filters__daily_log_segment_idNoQuery string parameter — daily Log Segment ID filter
Behavior5/5

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

Annotations already declare readOnly/ idempotent, and the description adds valuable context about date default behavior, pagination metadata, and required parameters. No contradictions.

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 reasonably concise and front-loaded with purpose, though it includes a link and API reference that could be trimmed. Still clear and efficient.

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?

No output schema exists, so description should elaborate on return fields; it only mentions 'paginated JSON array of Daily Log records' without specifics. Lacks completeness for a 9-parameter tool without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3; description adds value by explaining the effect of omitting date parameters and pagination controls, going beyond schema descriptions.

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 it returns Accident Logs for the current date and explains filtering options. It uses specific verb and resource, but does not explicitly differentiate from sibling tools like list_daily_construction_report_logs.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for use cases (enumerate, find IDs, filter) and mentions default behavior when no date parameters are provided, but lacks explicit exclusions or alternatives.

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