Skip to main content
Glama
TylerIlunga

Procore MCP Server

Remove Checklist Template Alternative Response Set

remove_checklist_template_alternative_response_set
Destructive

Remove the alternative response set from a checklist template to revert it to the default response set for inspections.

Instructions

Removes a Checklist Template's Alternative Response Set, returning the template to the default Response Set. Use this to update an existing Inspections (only the supplied fields are changed). Moves the Inspections to its new position and returns the updated object. Required parameters: id, project_id. Procore API: Project Management > Inspections. Endpoint: PATCH /rest/v1.0/checklist/list_templates/{id}/remove_alternative_response_set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — checklist Template ID
project_idYesJSON request body field — unique identifier for the project.
Behavior2/5

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

While the description correctly states it returns the updated object and provides the API endpoint, it contains contradictory and irrelevant information about updating inspections and moving objects. Annotations already indicate destructive behavior, but the description adds misleading context.

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

Conciseness1/5

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

The description includes two sentences that are clearly copy-pasted from another tool ('Use this to update an existing Inspections... Moves the Inspections to its new position'), which waste space and mislead the agent.

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

Completeness2/5

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

The description fails to provide a complete and accurate picture. It mentions reverting to default response set and returns updated object, but includes irrelevant and contradictory information that undermines completeness. No output schema exists, so description should clarify behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description merely repeats required parameters (id, project_id) without adding substantive meaning beyond what the schema already provides via their descriptions.

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?

The description clearly states the action: 'Removes a Checklist Template's Alternative Response Set, returning the template to the default Response Set.' This is a specific verb+resource, and it distinguishes from sibling tools like add and remove alternative response set variants.

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 includes confusing and likely copy-pasted sentences: 'Use this to update an existing Inspections (only the supplied fields are changed). Moves the Inspections to its new position and returns the updated object.' These do not relate to removing an alternative response set and do not guide when to use this tool versus alternatives.

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