Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Recycled Action Plan Template Receiver

show_recycled_action_plan_template_receiver
Read-onlyIdempotent

Retrieve a recycled action plan template receiver from a Procore project using its project ID and receiver ID. Returns the complete field set for a single read-only record.

Instructions

Retrieves a single recycled action plan template receiver in the specified Procore project. Use this when you already know which recycled action plan template receiver you want and need its full field set. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the recycled action plan template receiver. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id. Procore API: Project Management > Action Plans. Endpoint: GET /rest/v1.0/projects/{project_id}/recycle_bin/action_plans/plan_template_receivers/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — action Plan Template Receiver ID
project_idYesURL path parameter — unique identifier for the project.
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false; the description adds an explicit read-only statement, common failure modes (401/403/404), and the project_id defaulting behavior. This goes beyond annotations with useful operational context.

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?

Description is a single dense paragraph that front-loads the purpose, then provides usage, behavior, errors, and endpoint. Every sentence adds value, though it is slightly long and repeats the read-only annotation.

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?

For a single-resource GET with no output schema, the description covers return shape ('single JSON object'), failure modes, defaulting behavior, and prerequisite resolution. It names the Procore API path, making it complete enough for invocation.

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% with both parameters described. The description adds context (project_id default, id must resolve to an existing record), but the schema already documents the basic semantics. Baseline 3 is appropriate.

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?

States 'Retrieves a single recycled action plan template receiver in the specified Procore project' with a specific verb, resource, and scope. It clearly distinguishes from list tools by noting 'single' and 'full field set'.

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

Usage Guidelines5/5

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

Explicitly says 'Use this when you already know which recycled action plan template receiver you want and need its full field set' and instructs to resolve the id with 'the matching list tool first'. This clearly indicates when to use the tool and names the alternative.

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