Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Recycled Near Miss

show_recycled_near_miss
Read-onlyIdempotent

Retrieve full details of a recycled near miss incident using its project and incident identifiers. Returns a JSON object with incident information.

Instructions

Returns a specific Recycled Near Miss. Use this to fetch the full details of a specific Incidents by its identifier. Returns a JSON object describing the requested Incidents. Required parameters: project_id, id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/projects/{project_id}/recycle_bin/incidents/near_misses/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Incidents resource
incident_idNoQuery string parameter — unique identifier of the incident
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already convey read-only, idempotent, non-destructive behavior. The description adds that it's a GET request and the endpoint path, which provides minor additional context but is not essential.

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 (3 sentences) and front-loaded with the purpose. It includes endpoint details that are useful but could be more streamlined.

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?

The description fails to detail the response structure beyond 'JSON object describing the requested Incidents.' No output schema exists, so more specificity would help.

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 has 100% coverage with descriptions. The description redundantly states required parameters but adds that they are URL path parameters, which is already in 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 the tool returns a specific Recycled Near Miss and fetches full details, making the purpose unambiguous. The title and name also indicate a single-item retrieval.

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 indicates when to use the tool (fetch full details of a specific incident by identifier) but does not explicitly exclude cases or provide alternatives like list or retrieve siblings.

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