Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Observation Item Response Log

create_observation_item_response_log

Create a response log for an observation item in Procore. Use to record actions or notes on an observation by specifying item, project, and log details.

Instructions

Creates a new Response Log for a given Observation Item. Use this to create a new Observations in Procore. Creates a new Observations and returns the created object on success (HTTP 201). Required parameters: item_id, project_id, response_log. Procore API: Project Management > Observations. Endpoint: POST /rest/v1.0/observations/items/{item_id}/response_logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesURL path parameter — unique identifier of the item
run_configurable_validationsNoQuery string parameter — whether or not Configurable validations from the Observation Items Category Configurable Field Set should be run (default: false). See (https://developers.procore.com/reference/observations#list-ob...
project_idYesJSON request body field — the ID of the Project the Observation Item Response Log belongs to
response_logYesJSON request body field — response Log body
statusNoJSON request body field — the Status of the Observation
attachmentsNoJSON request body field — an array of the Attachments of the Observation Item Response Log. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-d...
Behavior3/5

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

Annotations already indicate non-readonly, non-destructive. Description adds HTTP 201 success context and required parameters but no additional behavioral details like side effects or authorization needs.

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 somewhat repetitive, mentioning 'Observations' twice in slightly different contexts. Could be more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers required parameters and API reference but lacks details on nested objects (response_log, attachments) and the response format. No output schema provided.

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% with good descriptions. Description mentions required parameters but does not add significant meaning beyond the schema. Baseline 3 applicable.

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?

Description clearly states it creates a new Response Log and returns the created object. Verb+resource is specific. Slight confusion with plural 'Observations' but overall 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 explicit guidance on when to use this tool vs alternatives. Among many sibling tools, no differentiation is 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