Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Send Unsent Task Items

send_unsent_task_items

Send email notifications for unsent task items in a Procore project. Provide project_id to dispatch the messages and get a confirmation response.

Instructions

Sends email notifications for unsent Task Items. 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: project_id. Procore API: Core > Tasks. Endpoint: POST /rest/v1.0/task_items/send_unsent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond annotations: it warns that calling again sends another copy (reinforcing idempotentHint=false), explains error payloads with HTTP status codes, and notes common failure modes (401, 403, 404). This goes well beyond the structured annotations.

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 three sentences, front-loaded with the main action, then behavior, error handling, and API endpoint. Every sentence adds value; redundant 'Required parameters: project_id' is minor but the overall structure is efficient.

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

Completeness5/5

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

For a single-parameter, non-idempotent tool with no output schema, the description covers the action, consequence of re-invocation, error responses, required parameter, and API location. It is sufficiently complete for an agent to invoke it correctly.

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%, so the baseline is 3. The description only restates that project_id is required and mentions the 404 case for an id, but adds no deeper meaning beyond what the schema's description already provides.

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 email notifications for unsent Task Items') with a specific verb and resource. It distinguishes from sibling send-unsent tools by referencing Task Items, and the endpoint/API reference further clarifies its scope.

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?

The context is clear (when you need to send notifications for unsent task items), and the non-idempotency warning informs usage. However, it does not explicitly name alternatives like send_unsent_punch_items or send_unsent_observation_items, so it lacks explicit exclusions.

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