Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Checklist Item

show_checklist_item
Read-onlyIdempotent

Retrieve full details of a specific inspection checklist item by providing list, item, project, and section IDs.

Instructions

Retrieves Checklist Item 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, section_id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/checklist/lists/{list_id}/items/{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.
section_idYesQuery string parameter — checklist Section 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 provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds endpoint and project area details but no behavioral context beyond 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?

Includes extraneous information (Procore API path) that could be omitted. Could be more concise by focusing on core purpose and omitting endpoint details.

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?

Lacks mention of optional pagination parameters (page, per_page) and return value details. Inconsistent naming ('Inspections') may mislead. For a tool with 6 parameters, more context is needed.

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 covers all 6 parameters with descriptions. The description lists required parameters but adds no additional meaning beyond what schema provides.

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

Purpose3/5

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

The description states it retrieves a 'Checklist Item' but incorrectly refers to 'specific Inspections' causing potential confusion. The verb 'Retrieves' is appropriate, but the inconsistency reduces clarity.

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, such as other list/show tools for checklists. Missing context on prerequisites or alternative scenarios.

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