Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Company Checklist Template

show_company_checklist_template
Read-onlyIdempotent

Retrieve detailed information about a specific Company Checklist Template using its ID and company ID. Access full template details for inspections management.

Instructions

Returns the details for a specified Company Checklist Template. Use this to fetch the full details of a specific Inspections by its identifier. Returns a JSON object describing the requested Inspections. Required parameters: company_id, id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/companies/{company_id}/checklist/list_templates/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — company Checklist Template ID
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, so safety is covered. Description adds endpoint info and required parameters, but does not disclose pagination behavior or other traits beyond what annotations provide.

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?

Description is fairly concise but contains redundancy (e.g., repeating 'Inspections' incorrectly) and could be more streamlined. It is front-loaded with the main purpose.

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?

No output schema is provided, and the description does not describe the response structure. Pagination parameters exist but are not mentioned in context. For a read operation, more detail about returned fields would be beneficial.

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%, so parameters are fully documented. Description repeats required params but adds no new semantic meaning such as formats or constraints beyond 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 it returns details for a Company Checklist Template, but it incorrectly refers to 'Inspections' (typo) which may cause slight confusion. The verb+resource pattern is clear.

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?

No guidance on when to use this tool vs alternatives. Among siblings, similar 'show_company_*' tools exist but no comparison or exclusion criteria are provided.

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