Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete A Time And Material Entry

delete_a_time_and_material_entry
DestructiveIdempotent

Permanently delete a time and material entry from a project. This removes field productivity records and cannot be undone.

Instructions

Deleting a Time And Material Entry 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, id. Procore API: Project Management > Field Productivity. Endpoint: DELETE /rest/v1.0/projects/{project_id}/time_and_material_entries/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — id of Time And Material Entry
Behavior4/5

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

Adds value beyond annotations by explicitly stating 'this cannot be undone' and 'permanently removes,' aligning with destructiveHint and readOnlyHint. No contradiction, and no extra behavioral details needed.

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?

Mostly concise, but contains redundancy ('cannot be undone' repeated twice). Still efficient with 4 sentences including API context.

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?

Covers purpose, irreversibility, required parameters, and API reference. Lacks mention of prerequisites like entry existence or permissions, but adequate for a simple delete tool.

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% with clear descriptions; the description only restates that project_id and id are required, adding no additional meaning.

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?

Clearly states the tool deletes a Time And Material Entry, distinguishing it from create, update, show, and list siblings. Uses specific verb 'delete' and resource 'Time And Material Entry'.

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?

Explicitly describes when to use (to permanently delete Field Productivity records) and emphasizes irreversibility. Does not mention when not to use or alternatives, but the warning is clear.

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