Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Observation Item

create_observation_item

Create a new observation item in Procore by providing project ID and observation details. Returns the created object on success.

Instructions

Create 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: project_id, observation. Procore API: Project Management > Observations. Endpoint: POST /rest/v1.0/observations/items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 belongs to
inspection_item_failedNoJSON request body field — 1 denotes that this Observation Item is being created from a failed Checklist Item. This will update the status of the Checklist Item to 'no' (fail). `observation[checklist_item_id]` must be provid...
observationYesJSON request body field — item object
attachmentsNoJSON request body field — [DEPRECATED] An array of the Attachments of the Observation Item. Please use upload_ids instead. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and ...
Behavior3/5

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

Description adds endpoint and return status beyond annotations. However, it omits side effects, permission requirements, or error conditions. Annotations already cover readOnly and destructive hints.

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

Conciseness5/5

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

Very concise, front-loaded with purpose. Four sentences, no fluff, easily scannable.

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?

Despite good schema coverage, the description lacks detail on the observation object structure, the inspection_item_failed field, and possible responses. For a creation tool with nested objects and no output schema, 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?

Input schema has 100% coverage, so parameter descriptions are already present. The description only lists required params without adding meaning beyond schema.

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?

Clearly states it creates an observation item and returns 201. However, it uses 'Observations' plural and does not differentiate from siblings like update_observation_item or list_observation_items.

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?

Provides no guidance on when to use this tool versus alternatives. No exclusions or prerequisites mentioned, leaving the agent to infer from context alone.

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