Skip to main content
Glama
Sign In
Contractor Foreman MCP Server

Contractor Foreman MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delete estimate

delete_estimate
Destructive

Permanently deletes an estimate and its line items; projects, change orders, and invoices created from it remain, and the action cannot be undone.

Instructions

Deletes an estimate for good.

Deletes the estimate and its line items, as Delete in the estimate's menu does. Records made from it (projects, change orders, invoices) stay. It cannot be undone. To keep the history, use update_estimate with status lost instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "estimate_id": "<estimate_id>"
    },
    "name": "delete_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
estimate_idYesFrom list_estimates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds what annotations cannot: line items are destroyed, downstream records (projects, change orders, invoices) survive, and the deletion mirrors the UI's Delete menu item. It also states irreversibility in plain words.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and consequence, then the cascade scope, then the safer alternative. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter destructive mutation with no output schema, everything an agent needs is present: what is destroyed, what is preserved, irreversibility, and the non-destructive alternative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the only parameter is documented as 'From list_estimates,' so the description need not repeat it. Baseline would be 3; the description earns a point for making clear the single identifier targets the estimate whose children are also deleted.

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?

States a specific verb and resource ('Deletes an estimate for good') and immediately disambiguates from sibling delete tools (delete_invoice, delete_change_order) by naming the exact object and its cascade semantics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not with a named alternative: 'To keep the history, use update_estimate with status lost instead.' An agent has a clear decision rule between hard delete and status change.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools