Skip to main content
Glama
TylerIlunga

Procore MCP Server

Deletes An Inspection Item Signature

deletes_an_inspection_item_signature
DestructiveIdempotent

Permanently remove a signature from an inspection item signature request. Specify company, project, item, and signature request IDs.

Instructions

Deletes an Inspection Item Signature for a specified Inspection Item 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: company_id, project_id, item_id, id. Procore API (v2.0): Project Management > Inspections. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/inspection_items/{item_id}/signature_requests/{id}/signature

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
item_idYesURL path parameter — unique identifier for the inspection item.
idYesURL path parameter — unique identifier for the inspection item signature request.
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds 'This cannot be undone' which aligns but does not provide additional behavioral context beyond what annotations convey. No contradiction found.

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 repetitive: 'This cannot be undone' appears twice, and 'permanently delete/removes' is stated twice. It also includes unnecessary repetition about required parameters already clear from schema. Could be more concise.

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 delete operation with 4 required parameters and good annotations, the description is adequate but confusing due to the mention of 'Inspections' instead of 'Inspection Item Signature'. Slightly incomplete in clarifying what exactly is deleted.

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 all 4 parameters. Description only repeats that they are 'Required parameters' and lists them, adding no new meaning. Baseline 3 is appropriate.

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

Purpose3/5

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

The description clearly states 'Deletes an Inspection Item Signature' but then confusingly refers to 'delete the specified Inspections' (plural). This inconsistency muddles the purpose. It also does not differentiate from sibling tools like 'deletes_an_inspection_item_signature_request'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., 'deletes_an_inspection_item_signature_request'). It only says 'Use this to permanently delete' but lacks exclusions or context for choosing this tool.

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