Skip to main content
Glama
TylerIlunga

Procore MCP Server

Send Observation Item Email

send_observation_item_email

Send an email for a specific observation item in a Procore project by supplying its ID and project ID, then confirm delivery and handle errors.

Instructions

Sends an email for an Observation Item in a Project. id must identify an existing parent record — resolve it with the matching list tool first. Dispatches the message and returns a confirmation; calling it again sends another copy. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: id, project_id. Procore API: Project Management > Observations. Endpoint: POST /rest/v1.0/observations/items/{id}/send_email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Observations resource
bodyNoJSON request body field — email Body
subjectNoJSON request body field — email Subject
project_idYesQuery string parameter — unique identifier for the Procore project
distribution_idsNoJSON request body field — array of distribution identifiers
cc_distribution_idsNoJSON request body field — array of cc distribution identifiers
bcc_distribution_idsNoJSON request body field — bcc_distribution_ids
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses that calling again sends another copy, returns a confirmation, and details common failure statuses (401, 403, 404). This meaningfully extends the annotation information.

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

Conciseness4/5

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

The description is dense but well-structured: action, precondition, behavior, error handling, and endpoint. It is slightly verbose with the endpoint line and required parameter listing that duplicates schema info, but each sentence carries useful information.

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

Completeness4/5

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

Given the tool's moderate complexity, the description covers the operation, id resolution requirement, non-idempotency, error handling, and API context. The lack of an output schema makes the 'confirmation' mention adequate, though it does not detail the full response shape.

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?

The schema provides 100% coverage for all 7 parameters, so the description is not required to repeat them. It does add context for the id parameter (must reference an existing parent record), which is helpful, but does not elaborate on the other parameters beyond the schema.

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

Purpose5/5

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

The description clearly states it sends an email for an Observation Item in a Project, using a specific verb and resource. It distinguishes itself from sibling tools like send_punch_item_email and send_unsent_observation_items by scoping to a single Observation Item.

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

Usage Guidelines4/5

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

It gives explicit guidance to resolve the id with the matching list tool first, establishing a clear precondition. It does not explicitly name alternatives or exclusions, but the context is sufficient for correct usage.

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