Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Signature

delete_signature_project_v1_0
DestructiveIdempotent

Delete a signature from a project's time and material entries by ID. Permanently removes the signature; verify the ID beforehand to avoid unintended loss.

Instructions

Deletes the Signature for the corresponding ID passed. Confirm the target id with the matching show or list tool before calling. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the signature. This cannot be undone, and a repeat call returns 404. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id. Procore API: Project Management > Field Productivity. Endpoint: DELETE /rest/v1.0/projects/{project_id}/time_and_material_entries/signatures/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Field Productivity resource
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

Goes well beyond annotations by disclosing permanence ('cannot be undone'), repeat-call behavior (404), and detailed error statuses (401/403/404). This is valuable context that annotations do not capture.

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 long but each sentence adds value: purpose, prerequisites, consequences, errors, required params, and API reference. Well-organized and front-loaded with the primary action.

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

Completeness4/5

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

Covers purpose, preconditions, deletion permanence, error handling, and endpoint. Although there is no output schema and success response is not described, for a delete operation this is adequate and 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 already has 100% parameter descriptions. The description adds meaning about project_id defaulting but creates a minor contradiction by calling project_id required while mentioning it can be omitted. It reiterates both parameters are required.

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?

The description clearly states 'Deletes the Signature for the corresponding ID passed' with the specific endpoint path, making the operation precise. It doesn't explicitly differentiate from sibling delete-signature tools, but the endpoint and resource context distinguish it.

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

Usage Guidelines4/5

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

Provides clear guidance on prerequisites: confirm the id with the matching show/list tool, resolve parent records first, and notes project_id defaults to configured value. However, it does not name explicit alternative tools or say when not to use 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