Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Monitoring Resource

delete_monitoring_resource
DestructiveIdempotent

Permanently delete specified Budget monitoring resources using project and resource IDs. This action cannot be undone.

Instructions

Delete Monitoring Resource. Use this to permanently delete the specified Budget records. This cannot be undone. Permanently removes the specified Budget records. This action cannot be undone. Required parameters: project_id, id. Procore API: Construction Financials > Budget. Endpoint: DELETE /rest/v1.0/projects/{project_id}/monitoring_resources/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — monitoring Resource ID
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. Description reinforces irreversibility ('cannot be undone'). No contradiction, but lacks details on failure scenarios or side effects like cascading deletes.

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 repetition: 'This cannot be undone' appears twice. Could be more concise without losing meaning. Adequate but not efficient.

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 two-parameter delete with no output schema, the description covers the core action and irreversibility. Missing details like error handling or prerequisites, but minimally complete.

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 covers both parameters with descriptions (100% coverage). Description adds minimal value by repeating 'URL path parameter' and 'monitoring Resource ID'—redundant with schema.

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?

Clearly states 'Delete Monitoring Resource' and specifies it deletes Budget records. However, does not differentiate from other delete tools in the sibling list; the purpose is clear but not unique.

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?

Explicitly says 'Use this to permanently delete the specified Budget records.' Mentions irreversibility, but no guidance on when to avoid or alternative tools. This is adequate for a straightforward delete.

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