Procore MCP Server

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

No annotations are provided, so the description carries the full burden. It mentions 'Bulk Create' and a POST endpoint, implying a write operation, but doesn't disclose behavioral traits like permissions needed, whether it's idempotent, or what happens on failure. This is inadequate for a mutation tool with zero annotation coverage.

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

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

The description is a single sentence but includes extraneous details like the API path ('POST /rest/v1.0/projects/{project_id}/action_plans/plan_template_approvers/bulk_create') and category tag ('[Project Management/Action Plans]'), which don't aid an AI agent. It's under-specified in meaningful content, not concise in a helpful way.

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

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

Given the complexity of a bulk creation tool with no annotations and no output schema, the description is incomplete. It fails to explain the return values, error handling, or prerequisites, leaving significant gaps for an agent to operate effectively.

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

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

Schema description coverage is 100%, with clear parameter descriptions (e.g., 'Unique identifier for the project'). The description adds no parameter semantics beyond the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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

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

The description states the action ('Bulk Create') and resource ('Action Plan Template Approvers'), but it's vague about what 'approvers' are and lacks specificity. It doesn't distinguish from sibling tools like 'bulk_create_action_plan_template_receivers' or 'bulk_create_action_plan_item_assignees', leaving the exact purpose unclear.

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

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

No guidance is provided on when to use this tool versus alternatives. With many sibling tools like 'create_action_plan_template_approver' (singular) and 'bulk_destroy_action_plan_template_approvers', the description offers no context for selection, making it misleading for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.