Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete A Person

delete_a_person
DestructiveIdempotent

Permanently delete a person from the company's Resource Planning records by providing company ID and person ID. This action cannot be undone.

Instructions

Deletes a Person for a given company and person ID. Use this to permanently delete the specified Resource Planning records. This cannot be undone. Permanently removes the specified Resource Planning records. This action cannot be undone. Required parameters: company_id, person_id. Procore API: Resource Management > Resource Planning. Endpoint: DELETE /rest/v1.0/workforce-planning/v2/companies/{company_id}/people/{person_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
person_idYesURL path parameter — unique identifier for the person

Tool Definition Quality

A4/5.0
Behavior4/5

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

Description emphasizes irreversibility ('This cannot be undone'), adding context beyond annotations which already indicate destructiveHint=true. 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?

Description is somewhat repetitive ('permanently delete' and 'cannot be undone' mentioned twice). Includes unnecessary API endpoint details, making it longer than needed.

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 tool with two parameters and no output schema, the description covers purpose, irreversibility, required parameters, and API context. Majority of relevant information is provided.

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 coverage is 100% with descriptions for both parameters. Description mentions they are required but adds minimal additional meaning beyond the schema.

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?

Clearly states the verb 'Deletes', the resource 'Person', and the scope ('for a given company and person ID'). Distinguishes from sibling delete tools by specifying it deletes Resource Planning records.

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 context for when to use the tool (permanently delete Resource Planning records). Does not explicitly state when not to use or list alternatives, but the purpose is clear.

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