Skip to main content
Glama
TylerIlunga

Procore MCP Server

Send Observation Item Email

send_observation_item_email

Send email notifications for Observation Items in a Procore project. Dispatch messages with custom subject, body, and distribution lists to confirm delivery.

Instructions

Sends an email for an Observation Item in a Project. Use this to dispatch the notification or message related to Observations. Dispatches the message and returns a confirmation. Repeated calls may resend. 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
project_idYesQuery string parameter — unique identifier for the Procore project
subjectNoJSON request body field — email Subject
bodyNoJSON request body field — email Body
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?

The description adds value beyond annotations by specifying that repeated calls may resend (aligning with non-idempotent hint) and providing the exact API endpoint. It does not contradict annotations and gives additional context about the operation's behavior.

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?

The description is concise, front-loaded with the main action, and includes useful details like required parameters and API endpoint without any redundant or irrelevant 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?

For a tool with 7 parameters and no output schema, the description covers purpose, behavior (resending), required parameters, and API reference. It could mention expected response format or error conditions, but overall it is sufficiently complete.

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 input schema has 100% coverage with descriptions for all 7 parameters. The description only highlights required parameters without adding extra meaning beyond what the schema already provides, so it meets the baseline.

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 the action ('Sends an email'), the resource ('Observation Item'), and the context ('in a Project'). It distinguishes this tool from siblings by specifying the exact function of dispatching a notification related to Observations.

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

Usage Guidelines3/5

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

The description implies usage for dispatching observation notifications but does not explicitly state when to avoid using this tool or mention alternatives. It notes that repeated calls may resend, but lacks exclusions or comparative guidance among sibling observation tools.

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