Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete Project Stage

delete_project_stage
DestructiveIdempotent

Permanently remove a project stage from a company's settings by specifying the company ID and stage ID. This deletion is irreversible.

Instructions

Delete the specified Project Stage. Use this to permanently delete the specified Company Settings. This cannot be undone. Permanently removes the specified Company Settings. This action cannot be undone. Required parameters: company_id, id. Procore API: Company Admin > Company Settings. Endpoint: DELETE /rest/v1.0/companies/{company_id}/project_stages/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — iD of the project stage

Tool Definition Quality

C2.9/5.0
Behavior3/5

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

Annotations indicate destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds permanence warning but does not explain idempotency or open world implications. No contradictions.

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?

Three sentences with some redundancy (e.g., 'This cannot be undone' repeated). API endpoint info adds context but could be more concise.

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?

For a simple delete without output schema, description covers essential aspects: irreversibility, required params, and API reference. Missing error scenarios or dependencies, but acceptable.

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 fully; description merely restates required parameters, adding no extra meaning beyond schema descriptions.

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 states 'Delete the specified Project Stage' which is clear, but later refers to 'Company Settings' causing confusion. The title and resource name are consistent, but the mixed terminology reduces clarity.

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?

No guidance on when to use this tool vs alternatives, such as other delete or deactivation tools. It notes permanence but lacks context for decision-making.

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