Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Recycled Witness Statement

show_recycled_witness_statement
Read-onlyIdempotent

Retrieve a specific recycled witness statement from the Incidents recycle bin using the project ID and witness statement ID.

Instructions

Returns a specific Recycled Witness Statement. 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 (v1.1): Project Management > Incidents. Endpoint: GET /rest/v1.1/projects/{project_id}/recycle_bin/incidents/witness_statements/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — witness Statement ID
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 declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read operation. The description adds the endpoint and required parameters but does not disclose any behavioral traits beyond what the annotations provide. No contradiction 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.

Conciseness3/5

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

The description is three sentences plus API metadata, which is reasonably concise. However, it contains a factual error ('Incidents' instead of 'Witness Statement') and includes redundant information already present in the schema and annotations. Could be tighter.

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 the tool's simplicity and the richness of annotations (readOnlyHint, etc.) and schema descriptions, the description adequately covers the tool's function, required parameters, and API endpoint. It acknowledges the return format as JSON, which is sufficient without an output schema.

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?

The input schema has 100% description coverage, providing clear meanings for all parameters. The description only repeats the required parameters (project_id, id) without adding further context or compensating for any gaps. Baseline score of 3 is appropriate.

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 that the tool returns a specific Recycled Witness Statement. However, it inaccurately refers to 'Incidents' instead of 'Witness Statement', causing slight confusion. It does not explicitly differentiate from sibling tools like show_recycled_incident or show_witness_statement.

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 only says 'Use this to fetch the full details...' without providing guidance on when to use this tool versus alternatives. There is no mention of exclusions or comparative context, which is insufficient given the many sibling tools for showing recycled items.

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