Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete Equipment Log

delete_equipment_log
DestructiveIdempotent

Permanently delete a single equipment log record from Daily Log. Requires project and log ID.

Instructions

Delete single Equipment Log. Use this to permanently delete the specified Daily Log records. This cannot be undone. Permanently removes the specified Daily Log records. This action cannot be undone. Required parameters: project_id, id. Procore API: Project Management > Daily Log. Endpoint: DELETE /rest/v1.0/projects/{project_id}/equipment_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Daily Log resource

Tool Definition Quality

A3.9/5.0
Behavior4/5

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

Reinforces destructiveHint=true with 'cannot be undone' and 'permanently removes'. Adds endpoint info and required params, providing context beyond annotations.

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?

Contains redundancy (repeats 'This cannot be undone' twice). Includes API endpoint which may be unnecessary. Could be more streamlined.

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?

Covers key aspects: purpose, permanence, required params. Lacks info on error handling or response when log doesn't exist, but sufficient for a simple delete operation.

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 has 100% coverage with clear descriptions. Description only lists required params without adding new semantic insight, meeting 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?

Clearly states it deletes a single Equipment Log and specifies it's for Daily Log records. Distinguishes from sibling delete tools targeting other equipment-related resources.

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?

Tells when to use it (to permanently delete records) but omits when not to use or mention alternatives. However, the specific resource makes usage unambiguous.

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