Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Checklist Item Response

create_checklist_item_response

Create a response for a Procore inspection checklist item, submitting the appropriate value type based on the item (text, number, date, response option, or status).

Instructions

Create Checklist Item Response for a specified Checklist Item Checklist Item Response can have one of the following payload formats (text_value, number_value, date_value, response_option, status) A specific Item Type can only leverage its corresponding format. *For instance, Number Items can only leverage a number_value while Date Items can only leverage a date_value. Use this to create a new Inspections in Procore. Creates a new Inspections and returns the created object on success (HTTP 201). Required parameters: item_id, project_id. Procore API: Project Management > Inspections. Endpoint: POST /rest/v1.0/projects/{project_id}/checklist/items/{item_id}/item_response

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesURL path parameter — unique identifier of the item
project_idYesURL path parameter — unique identifier for the project.
statusNoJSON request body field — item Status - Value for Default-Typed items. Allowed values are 'conforming', 'non_conforming', and 'not_applicable'.
response_option_idNoJSON request body field — response Option ID - Value for Multiple Choice Response Items
text_valueNoJSON request body field — text Response - Value for Open Ended Text Items
number_valueNoJSON request body field — number Response - Value for Open Ended Number Items
date_valueNoJSON request body field — date Response - Value for Open Ended Date Items. Format should be YYYY-MM-DD
Behavior3/5

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

The description indicates a write operation (create) and mentions HTTP 201 on success, consistent with readOnlyHint=false. However, no additional behavioral traits beyond creation are disclosed, such as error handling or permission requirements.

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 moderately concise but contains repetition and an erroneous sentence about creating inspections. It is front-loaded with the purpose but lacks streamlined structure.

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?

Missing critical context such as error scenarios, prerequisites, and the actual return value (no output schema). The inclusion of incorrect information further detracts from completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds value beyond the schema by explaining that payload formats correspond to item types (e.g., number_value for number items). This clarifies the conditional usage of parameters.

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 the tool creates a checklist item response and lists payload formats, but includes a misleading phrase about creating a new Inspections, which reduces clarity. It does not differentiate from siblings like create_checklist_inspection.

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 is provided on when to use this tool versus alternatives. The misleading statement 'Use this to create a new Inspections' is inaccurate and offers no real usage context.

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