Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Checklist Signature

delete_checklist_signature
DestructiveIdempotent

Permanently delete a signature from a Procore checklist signature request. Use to remove an unwanted or incorrect signature from inspection checklists.

Instructions

Deletes a Signature for a specified Checklist Signature Request. Use this to permanently delete the specified Inspections. This cannot be undone. Permanently removes the specified Inspections. This action cannot be undone. Required parameters: list_id, signature_request_id, project_id. Procore API: Project Management > Inspections. Endpoint: DELETE /rest/v1.0/checklist/lists/{list_id}/signature_requests/{signature_request_id}/signature

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesURL path parameter — unique identifier of the list
signature_request_idYesURL path parameter — checklist Signature Request ID
project_idYesQuery string parameter — unique identifier for the project.
Behavior1/5

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

The description is misleading by stating it deletes inspections; it adds no behavioral context beyond the annotations (destructiveHint) and even suggests incorrect behavior.

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

Conciseness2/5

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

The description is redundant, repeating 'This cannot be undone' and 'Permanently removes the specified Inspections' twice, and includes non-essential info like the endpoint.

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

Completeness1/5

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

The description is incomplete and misleading; it fails to clarify that it deletes a signature (not inspections) and omits prerequisites or side effects beyond annotations.

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 100% of parameters with descriptions; the description lists required parameters but adds no additional meaning, meeting baseline expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it deletes a signature but repeatedly says 'permanently delete the specified Inspections', which is misleading and conflates signatures with inspections.

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

Usage Guidelines1/5

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

The description incorrectly directs users to use this tool to delete inspections, providing no guidance on when to use this tool versus alternatives like delete_checklist_inspection or delete_checklist_signature_request.

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