Skip to main content
Glama
TylerIlunga

Procore MCP Server

show_project_inspection_template_item_reference

Retrieve a specific item reference from a project inspection template in Procore to access detailed inspection criteria and requirements.

Instructions

Show Project Inspection Template Item Reference. [Project Management/Inspections] GET /rest/v1.0/projects/{project_id}/inspection_templates/{inspection_template_id}/item_references/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
inspection_template_idYesThe ID of the Project Inspection Template
idYesThe ID of the Project Inspection Template Item Reference
pageNoPage number for pagination
per_pageNoItems per page (max 100)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Show' and includes a REST endpoint, implying a read-only operation, but does not clarify permissions, rate limits, or response format. This is inadequate for a tool with potential complexity.

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 is concise with two sentences, but it is not front-loaded with useful information. The first sentence is tautological, and the second includes a REST endpoint that may not be necessary for an AI agent, making it somewhat inefficient.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'Show' entails (e.g., retrieving details, pagination behavior, or error handling), leaving significant gaps for a tool with five parameters and no structured output documentation.

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 description coverage is 100%, so the input schema fully documents all parameters. The description adds no additional parameter semantics beyond what the schema provides, which is acceptable given the high coverage, resulting in a baseline score of 3.

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 'Show Project Inspection Template Item Reference' is a tautology that restates the tool name without adding clarity. It lacks a specific verb and resource context beyond what's implied by the name, failing to distinguish its purpose from sibling tools.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent with no usage instructions.

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