Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Near Misses

list_near_misses
Read-onlyIdempotent

Retrieve a paginated list of near misses for a project. Use filters to narrow results by incident, company, person, or date range.

Instructions

Returns a list of Near Misses for a given project. Use this to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Incidents. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/projects/{project_id}/incidents/near_misses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
incident_idNoQuery string parameter — incident ID. When provided, the list will be scoped to only the Near Misses for a given Incident.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__created_atNoQuery string parameter — return 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_idNoQuery string parameter — array of Company IDs. Returns item(s) with the specified affected Company IDs.
filters__affected_party_idNoQuery string parameter — array of Affected Party IDs. Returns item(s) with the specified Affected Party IDs.
filters__affected_person_idNoQuery string parameter — array of Person IDs. Returns item(s) with the specified affected Person IDs.
filters__harm_source_idNoQuery string parameter — array of Harm Source IDs. Returns item(s) with the specified Harm Source IDs.
filters__work_activity_idNoQuery string parameter — array of Work Activity IDs. Returns item(s) with the specified Work Activity IDs.
filters__managed_equipment_idNoQuery string parameter — return item(s) with the specified Managed Equipment ID.
filters__queryNoQuery string parameter — return item(s) containing query
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is covered. The description adds pagination details (page/per_page, metadata) and endpoint info, but does not disclose additional behavioral traits beyond what annotations imply.

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 relatively concise with about five sentences, front-loaded with purpose. However, there is some redundancy (e.g., 'Returns a list' followed by 'Returns a paginated JSON array'). It could be tighter.

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?

No output schema is provided, so the description should accurately explain the return value. It says 'Returns a paginated JSON array of Incidents' but the tool is for Near Misses, creating confusion. It also does not detail the structure of near miss objects or cover all filter parameters, leaving gaps.

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 coverage is 100%, so the baseline is 3. The description mentions page, per_page, and project_id, but these are already documented in the schema. No additional semantic meaning is provided beyond what the schema offers.

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

Purpose3/5

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

The description states it returns a list of Near Misses for a project, but then conflates with Incidents by saying 'enumerate Incidents' and 'Returns a paginated JSON array of Incidents.' This inconsistency undermines clarity and could mislead an agent about what is actually returned.

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?

The description provides clear context for when to use the tool: 'when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not explicitly exclude scenarios or name alternatives, which is acceptable given the broad sibling list.

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