Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Checklist Comment

show_checklist_comment
Read-onlyIdempotent

Retrieves a specific comment from a Procore inspection checklist using list, comment, and project IDs.

Instructions

Retrieves Checklist Comment in a specified Checklist. Use this to fetch the full details of a specific Inspections by its identifier. Returns a JSON object describing the requested Inspections. Required parameters: list_id, id, project_id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/checklist/lists/{list_id}/comments/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesURL path parameter — unique identifier of the list
idYesURL path parameter — unique identifier of the Inspections resource
project_idYesQuery string 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 declare readOnlyHint and idempotentHint, so the description's addition of the API category and endpoint adds minor context. However, no further behavioral details (e.g., pagination behavior, return format) are provided. Does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description contains redundancy (required parameters) and a misleading line about 'Inspections'. It is not concise and includes confusing content that detracts from clarity.

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 exists, so the description should clarify return values. It mentions 'JSON object describing the requested Inspections' but the tool is about comments, making it incomplete and misleading. Pagination parameters exist but are not explained.

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%; all parameters are documented in the schema. The description redundantly lists required parameters but adds no new meaning or usage hints beyond what the schema provides, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it retrieves a 'Checklist Comment' but then describes fetching 'Inspections', which is contradictory. The tool name and endpoint imply it is about comments, not inspections, leading to confusion about the tool's actual purpose.

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 versus alternatives. The description simply states 'Use this to fetch...' without explaining context or excluding scenarios. Given 200+ sibling tools, differentiation is absent.

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