Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete A Time And Material Notification

delete_a_time_and_material_notification
DestructiveIdempotent

Permanently delete a time and material notification for a project. Requires project ID. This action cannot be undone.

Instructions

Deleting a Time And Material Notification associated with the specified project. Use this to permanently delete the specified Field Productivity records. This cannot be undone. Permanently removes the specified Field Productivity records. This action cannot be undone. Required parameters: project_id. Procore API: Project Management > Field Productivity. Endpoint: DELETE /rest/v1.0/projects/{project_id}/time_and_material_notifications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Annotations already convey destructiveHint=true and readOnlyHint=false. The description adds emphasis on irreversibility but no new behavioral context beyond stating it cannot be undone.

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?

The description is slightly repetitive (two mentions of 'permanently delete/removes') and includes peripheral info like API path. It could be more concise.

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?

For a simple delete tool, the description covers basic purpose and required input. It does not describe return values, but that is acceptable for a delete operation. Missing context about authentication or side effects.

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% and the description merely restates the required parameter without adding semantic meaning beyond what the schema provides.

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?

The description clearly states it deletes a Time And Material Notification associated with a project, using a specific verb and resource. It distinguishes from sibling tools like create, update, and show.

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 indicates to use it for permanent deletion but does not provide guidance on when not to use it or suggest alternatives among sibling tools. It only specifies required parameters.

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