Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Project Checklist Template

show_project_checklist_template
Read-onlyIdempotent

Retrieve the full details of an inspection checklist template by its ID and project ID. Returns a JSON object with the template data.

Instructions

Shows an Inspection Checklist Template. Note: A User with read-only and above permissions to Inspections has access to this endpoint and the URL to the template on the web. Use this to fetch the full details of a specific Inspections by its identifier. Returns a JSON object describing the requested Inspections. Required parameters: id, project_id. Procore API (v1.1): Project Management > Inspections. Endpoint: GET /rest/v1.1/projects/{project_id}/checklist/list_templates/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — checklist Template ID
project_idYesURL path parameter — unique identifier for the project.
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 indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds minor context about permissions and endpoint info, but does not significantly enhance transparency.

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 includes some extraneous details like full API path and version, which could be omitted. It is not overly long but could be more focused on essential information.

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?

The tool accepts pagination parameters (page, per_page) but the description says it fetches 'full details of a specific Inspections', implying a single item. This inconsistency is not addressed. No output schema is provided, and the description does not clarify the return structure beyond 'JSON object'.

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?

Input schema has 100% coverage with descriptions for all 4 parameters. The description only restates the required parameters without adding new semantic meaning beyond the schema.

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 the tool shows an Inspection Checklist Template and fetches full details by identifier. The verb 'shows' and resource are specified, but it does not explicitly differentiate from sibling tools like 'show_checklist_template' or 'show_company_checklist_template'.

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 mentions access permissions (read-only and above) and the endpoint availability, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it.

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