Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Recycled Near Misses

list_recycled_near_misses
Read-onlyIdempotent

Retrieve a paginated list of recycled near misses for a Procore project or specific incident. Supports filtering by date, company, person, and other criteria to locate incident records.

Instructions

Returns a list of Recycled Near Misses for a given project (or Incident, if incident_id is present). 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}/recycle_bin/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 Recycled Near Misses for a given Incident.
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
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint. The description adds context about pagination (page, per_page), metadata in response, and the API endpoint details. No contradictions with annotations.

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 concise and front-loaded with the purpose. It contains no unnecessary words. However, it could be slightly more streamlined by combining some sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters, full schema coverage, and no output schema, the description covers purpose, usage, pagination, required parameters, and API endpoint. It does not detail return values, but this is acceptable per rules since no output schema exists.

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 parameters. The description adds minimal extra value by mentioning 'Required parameters: project_id' and pagination controls, but this does not significantly enhance understanding beyond the schema.

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

Purpose5/5

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

The description clearly states it returns a list of Recycled Near Misses for a given project or incident. The verb 'list' and resource 'Recycled Near Misses' are specific. It distinguishes from active near misses by explicitly including 'recycled' in the name and description.

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

Usage Guidelines3/5

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

The description provides guidance on when to use: 'to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters.' It mentions required and optional parameters but does not explicitly state when not to use or contrast with alternatives like list_near_misses.

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