Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Weather Log

delete_weather_log_project
DestructiveIdempotent

Permanently delete a specific weather log entry from a Procore project. Requires project ID and log ID.

Instructions

Delete single Weather 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 (v1.1): Project Management > Daily Log. Endpoint: DELETE /rest/v1.1/projects/{project_id}/daily_logs/weather_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
Behavior4/5

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

Annotations already indicate destructiveHint=true; the description adds value by explicitly stating irreversibility ('cannot be undone') and the HTTP method, but does not disclose additional traits like required permissions or side effects.

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?

The description is concise with purpose front-loaded, though it repeats 'cannot be undone' twice, making it slightly redundant.

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?

The description covers core behavior but lacks details on return values, idempotency (despite annotation), and prerequisite conditions, which is acceptable 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?

Input schema has 100% coverage with descriptions for both parameters; the description merely restates them as 'Required parameters' without adding new semantic information.

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 'Delete single Weather Log' and specifies it permanently removes Daily Log records, distinguishing it from other weather log tools (create, update, list).

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 when to use (for permanent deletion) but does not provide explicit exclusions or alternatives, leaving the agent to infer from sibling 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